Sign in with Google and Facebook: what controls the buttons and what users see

Purpose#

The sign-in page of a company website can show two buttons: Google and Facebook. The link to the providers is really implemented with the Socialite library. This page explains what controls the two buttons, what the Social login settings screen in the company panel does and does not control, and what a visitor sees and what happens when a button is pressed.

What controls the buttons#

• Whether the buttons appear on the sign-in page, and which app credentials are used when a visitor presses one, come from the platform-level social sign-in settings. The sign-in page, the step that sends the visitor to the provider and the step that receives the visitor back all read those settings.
• The values saved on your own company's Social login settings screen are not the ones those steps read. So do not rely on saving them there to switch the buttons on or off on your company's sign-in page.
• If you want Google or Facebook sign-in on your company's sign-in page, contact the platform administrator (platform support) and ask them to enable it.
• The sign-in page of the main platform domain does not show these buttons; they appear only on a company-domain sign-in page.

Who can access the company screen#

• The screen works on the company domain only, under Setting > Social login settings. You need social_login_settings_read to open it and social_login_settings_update to save.
• The menu item Social login settings sits in the Setting group and shows for accounts with social_login_settings_update (the Setting group itself needs at least one read permission among delivery categories, charges, types, liquid/fragile and packaging).

What the screen contains#

Two independent cards, each with its own Save Change button:

The screen shows and saves the values stored for your company. Saving only updates values that already exist for your company; if there are none, the fields appear empty and Save Change ends with an error message whose text reads parcel.error_msg instead of saving. Do not rely on this screen to enable social sign-in; ask the platform administrator.

How to get social sign-in on your sign-in page#

1. Check the sign-in page

   Open your company's sign-in page in a private window. If an "or" divider with a Facebook and/or Google button appears below the Login button, those providers are on at platform level. If nothing appears, they are not enabled.

2. Ask the platform administrator

   Contact the platform administrator (platform support) and ask them to enable Google or Facebook sign-in for your company, and give them your company's domain. The platform builds the return address from the domain the visitor is on, https://YOUR-COMPANY-DOMAIN/google/login and https://YOUR-COMPANY-DOMAIN/facebook/login, and the provider's app has to list these addresses for every domain in use.

3. Test from the sign-in page

   Once they confirm, open the sign-in page in a private window and check that the button appears and sign-in completes.

What users see and what happens#

• Below the Login button there is an "or" divider and then a Facebook and/or Google button, only for providers that are on, on a company-domain sign-in page.
• Pressing a button sends the user to the provider, who then returns to the callback address. If an account is linked to the provider's ID, that user is signed in and sent to the home page.
• If none is found, the system automatically creates a new merchant account in the company from the name, email and picture supplied by the provider, with a random password. It also creates the merchant record, two wallets with a zero balance, a default shop and a copy of your company's delivery charges, and then signs the user in.
• Matching is by the provider's ID only: an existing account with the same email is not linked, and company staff or couriers cannot sign in this way, because the ID is stored only on accounts this flow created.
• If the provider is off, the message is "Google login is not enabled." or "Facebook login is not enabled.". Any other failure (the user declines, wrong credentials...) returns the user to the previous page with a message showing the raw text parcel.error_msg.

Common mistakes#

• Expecting the company screen to switch the buttons on. The buttons on your company's sign-in page follow the platform-level settings, not this screen; ask the platform administrator to enable them.
• A callback address that does not match the domain. The provider rejects it with its own message, and the platform shows nothing more specific than the generic message.
• Expecting staff or couriers to sign in this way. The flow is meant for merchant accounts that it creates itself.
• Expecting an old account to be linked by email. A separate new merchant account is created.
• Looking for the buttons on the merchant sign-up page. The merchant sign-up page of a company site has no Google or Facebook buttons.

Limits and permissions#

• The buttons follow the platform-level settings; the company screen holds your company's own values and may not save for every company.
• It works on company domains only and creates merchants only.
• For other merchant registration paths see the guide "Register a new merchant account".