> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form/social-sign-in/line-sign-in.md).

# LINE Sign-in configuration

Configure LINE Login and connect it to The Wallet Crew social sign-in.

Use this page to enable the **LINE** button in an enrolment form.

Start with [Social sign-in](/guides-enrolment/enrolment/enrolment-form/social-sign-in.md) to understand the customer flow. Then come back here for the provider setup.

<div data-with-frame="true"><figure><img src="https://831874859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlFokgwgJiwLXu7G8MVSJ%2Fuploads%2FrnwcyjXmmVCc5Ox8KaxD%2FLine-Social-Sign-In.png?alt=media&#x26;token=9bd59ac9-ced4-4396-b440-c6c8a0d88f7f" alt="LINE-Social-Sign-In-Example" width="375"><figcaption><p>Connect with LINE in an enrolment form example</p></figcaption></figure></div>

### Overview

#### What is set up here

* A LINE channel with the LINE Login product enabled.
* **Allowed OAuth redirect URIs** and **valid domains** for the enrolment form.
* The App ID stored in **The Wallet Crew** admin console.

#### Prerequisites

* Access to the brand’s **LINE Developers Console**.
* Permission to create and manage **channels**.
* The list of domains where the enrolment forms will run (prod + staging + dev + custom).

### Create the LINE channel

{% stepper %}
{% step %}

#### **Create a provider and channel**

Go to the LINE Developers Console

<p align="center"><a href="https://developers.line.biz/console" class="button secondary" data-icon="chevrons-right">LINE Developers Console</a></p>

1. Select or create a **Provider**
2. Click **Create a new channel**
   {% endstep %}

{% step %}

#### **Select LINE Login**

<figure><img src="https://831874859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlFokgwgJiwLXu7G8MVSJ%2Fuploads%2FzRtoLAjl87ZrBdPXNnCb%2Fenroll-line-sign-select-line-login.png?alt=media&#x26;token=2cada1fc-c6d9-4e6e-89e7-7de19ad347ae" alt="Channel type selection in the LINE Developers Console"><figcaption><p>Check that LINE Login is selected before creating the channel.</p></figcaption></figure>

1. Choose **LINE Login**
2. Select app type: **Web app**
3. Fill the required information
4. Create the channel
   {% endstep %}

{% step %}

#### **Enable Email permission (OpenID Connect)**

Open the channel settings:

<figure><img src="https://831874859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlFokgwgJiwLXu7G8MVSJ%2Fuploads%2F3cSWPlMSPFzx6MYS7OLN%2Fenroll-line-sign-enable-email-permission-openid-connect.png?alt=media&#x26;token=a21eaf0d-6e73-416a-a023-7747931ce29b" alt="OpenID Connect section of a LINE Login channel"><figcaption><p>Check that email address permission is applied for and granted.</p></figcaption></figure>

1. Go to the **OpenID Connect** section
2. Enable **Email address permission**

This step is required when the enrolment flow depends on email.
{% endstep %}

{% step %}

#### **Configure callback URLs**

In the **LINE Login** tab:

Add a callback URL for each environment:

```http
https://app.neostore.cloud/auth/callback/line
https://app-qa.neostore.cloud/auth/callback/line
https://app-dev.neostore.cloud/auth/callback/line
https://<your-custom-domain>/auth/callback/line
```

Important:

* The full URL must match exactly
* Include `/auth/callback/line`
* Add prod + QA + dev + custom domains

Save the changes.
{% endstep %}

{% step %}

### Publish the channel

In the top-left corner, click **Developing**.

<figure><img src="https://831874859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlFokgwgJiwLXu7G8MVSJ%2Fuploads%2FIBlNPuMFOzYfcJ9ninsN%2Fimage.png?alt=media&#x26;token=961732ab-42f1-4551-8120-9bc5446244cf" alt="Channel status control in the LINE Developers Console"><figcaption><p>Check that the channel status moves from Developing to Published.</p></figcaption></figure>

Then click **Publish** to make the channel available for production use.
{% endstep %}
{% endstepper %}

### Configure LINE in The Wallet Crew

In The Wallet Crew Backoffice, open the LINE configuration page.

<p align="center"><a href="https://admin.thewalletcrew.io/tenant/~/settings/social/line" class="button secondary" data-icon="chevrons-right">Social Login -> LINE</a></p>

<div data-with-frame="true"><figure><img src="https://831874859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlFokgwgJiwLXu7G8MVSJ%2Fuploads%2F4X77x3KUfEabMRWpCvUy%2Fimage.png?alt=media&#x26;token=58026a2f-534e-4b09-b2ca-7c10e455a50e" alt="The Wallet Crew - LINE configuration screen" width="563"><figcaption><p>LINE configuration screen</p></figcaption></figure></div>

Copy the values from the LINE Developers Console into The Wallet Crew.

After saving, keep this page open for a quick cross-check:

* The LINE channel must be the same one used for the callback URLs.
* The saved `clientId` must match the **Channel ID** exactly.

{% hint style="info" %}
These values are available in:

LINE Developers Console → the channel → **Basic settings**
{% endhint %}

### Enable LINE on the enrolment form

Enable the provider in the enrolment form settings.

Go into `advanced configuration -> Layout`. Open the layout where social sign-in should be activated and add these lines:

<pre class="language-yaml"><code class="lang-yaml"><strong>signinOptions:
</strong>  providers:
    - type: line
</code></pre>

For more information see [Enrolment form](/guides-enrolment/enrolment/enrolment-form.md).

### FAQ

<details>

<summary>Which LINE channel type should I create for this setup?</summary>

Create a **LINE Login** channel with app type **Web app**.

That’s the channel type that supports the OAuth callback flow used by enrolment forms.

</details>

<details>

<summary>Do I need to enable “Email address permission” in OpenID Connect?</summary>

Enable it when the enrolment flow requires an email.

Without it, LINE may not return an email for the customer.

</details>

<details>

<summary>What callback URLs do I need to add?</summary>

Add one callback URL per environment.

The URL must match exactly and must include `/auth/callback/line`.

Use the patterns listed above for prod, QA, dev, and any custom domain.

</details>

<details>

<summary>Where do I find the LINE <code>clientId</code> ?</summary>

In the LINE Developers Console:

**The channel → Basic settings**.

Copy the **Channel ID** into `authentication.clientId`.

</details>

<details>

<summary>How do I actually show the LINE button on the enrolment form?</summary>

Enable the provider in the **enrolment form settings**.

When buttons are managed via layout YAML, add `- type: line` under `signinOptions.providers`.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form/social-sign-in/line-sign-in.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
