Social login
Adds a Continue with… button to your storefront sign-in, so visitors can use an account they already have rather than waiting for a verification code.
| Section | Settings → Accounts |
| Panel route | /admin/social-login |
| Access needed | Platform → Social Credential → View list |
How it works
Each provider is a card you configure separately: Google, Apple and Kakao.
The Kakao card is on the screen, but its settings are rejected when you save them. Use Google or Apple for now.
A card shows the client ID (or No client ID added yet), how many mobile app IDs it has, an Enabled switch that works once a client ID is saved, and Set up (Edit once configured).
| Status | Meaning |
|---|---|
| Active | Enabled and configured — the button shows on your storefront |
| Disabled | Configured but switched off |
| Not configured | No client ID added yet |
Configuring a provider
Set up on a provider card opens its configuration.
| Field | Notes |
|---|---|
| Enable {provider} login | Shows the Continue with… button on your storefront |
| Client ID | From the provider's own console. Required to enable |
| Client secret | From the same place. Leave blank when editing to keep the current one |
| Mobile app IDs | Optional extra IDs whose tokens should be accepted, comma separated, up to 10 |
| Return URL to register | Shown for Apple and Kakao — register this exact address in the provider's console. Google has none to register |
The screen links straight to each provider's developer console.
The screen shows the exact address to register. A provider will refuse sign-ins from an address it does not recognise, so copy it exactly.
Mobile app IDs
| Provider | Use it for |
|---|---|
| Apple | Your iOS app's bundle ID, so Sign in with Apple from the app is accepted |
| Extra client IDs whose tokens should be accepted — the app normally uses the Client ID above | |
| Others | Extra client IDs whose tokens should be accepted |
The card shows how many mobile app IDs a provider has.
Order of work
Enabling before the provider's side is ready means a button that fails.
What customers see
On the sign-in screen, a divider and a Continue with… button for each active provider, alongside the usual verification-code sign-in. Their first social sign-in creates their account.
Scenarios
Reduce sign-up drop-off
Enable the one provider your customers actually use. One working button beats four.
You have an iOS app
Configure Apple, and add your app's bundle ID under mobile app IDs so in-app sign-in is accepted.
A provider's button has stopped working
Its credentials changed, or the Return URL is no longer registered. Check the provider's console, then re-enter the client ID and secret here.
Questions
Can I enable a provider without a client ID? No. The form requires one.
Is my client secret shown back to me? No. Leave it blank when editing to keep the current one.
Does social sign-in skip my registration fields? No. A new customer still completes the sign-up form, with every field you show and require in Registration Fields.
Can I disable a provider without deleting its credentials? Yes — switch Enabled off on its card. The status becomes Disabled.
Related
- Add your team — how people get into your platform
- Registration Fields · Users · Mobile App Settings