Google and LinkedIn Sign-in
Google and LinkedIn sign-in let students, applicants and other non-staff users sign in to Full Fabric, or create their account, with an existing Google or LinkedIn account instead of a password. Each provider uses an OAuth client that your institution registers with Google or LinkedIn. When enabled, the login and sign-up pages show Continue with Google and Continue with LinkedIn buttons, and Google can also offer its One Tap prompt. Staff and administrators always sign in another way.
Note: This page covers setting up the two providers and what people see. The login flow as a whole is in Authentication, and how the login page's Continue chooses between Google, LinkedIn, SAML and the password field is in SSO / SAML.
How It Works
Setting Up a Provider
Go to Settings → Access & security → Authentication. The Authentication Providers list shows every sign-in method with its Provider, Enabled and Login routing columns. Every institution has one Google provider (named Google oAuth 2.0) and one LinkedIn provider; click one to open its Edit page.
The page autosaves: text fields save when you leave them, the Enabled toggle saves straight away. The settings only appear while Enabled is on:
- General: the provider's display Name in the list
- Credentials: the OAuth client credentials issued by the provider
| Field | Notes | ||
|---|---|---|---|
| Client ID | Required | Required | From the provider's developer console |
| Client secret | Required | Required | Masked as you type |
| Redirect URI | Not shown | Optional | Only when your LinkedIn app is registered with a different callback address than your Full Fabric address |
Create an OAuth client in the Google Cloud console and register your Full Fabric address followed by /auth/google/callback as an authorised redirect URI, for example https://apply.school.edu/auth/google/callback. Copy its client ID and secret into the provider. New institutions start with the Google provider disabled and empty.
New institutions start with the LinkedIn provider disabled but with Full Fabric's LinkedIn app credentials already filled in. To use your own LinkedIn app instead, give it the openid, profile and email scopes (Full Fabric requests these), register your Full Fabric address followed by /auth/linkedin/callback as its redirect URL, and replace the Client ID and Client secret. If your app is registered with another callback address, enter it in Redirect URI.
Enabling and ordering
The login page shows the provider's button as soon as Enabled is on, so fill in the credentials straight after switching it on. An enabled provider without a client ID and secret shows a warning on its page ("Sign-in will fail until it is completed") and Not set up. Add the client ID and client secret. under Login routing.
Drag providers in the list to change the order Continue tries them in. Google and LinkedIn are only reached by Continue when they sit above Email & Password; their buttons work wherever they sit.
What People See
The login page shows Continue with LinkedIn and Continue with Google above the email field, and the sign-up page offers them as alternatives. When the person has already typed their email address, Google preselects that account.
Google One Tap: when the Google provider is enabled and has a client ID, the login page also shows Google's One Tap prompt. Picking an account there signs in exactly like the Continue with Google button. The prompt is not shown during the second-factor or passkey step, and Google accounts without a verified email address are refused.
First sign-in and account linking
Full Fabric matches the identity coming back from the provider like this:
| Situation | What happens |
|---|---|
| Google, and an active non-staff account exists for the Google address | The account is linked to that Google account and signed in, whether or not it has a password |
| LinkedIn account already linked to a Full Fabric account | Signed in |
| LinkedIn, and an active account without a password exists for the address but is not linked | Refused with a message (see below); Continue then emails a sign-in link |
| No account for the address, or one that never finished signing up | The Almost there screen, to create the account |
| LinkedIn, and an account with a password exists but is not linked | The Almost there screen, to link it |
| A staff or administrator account | Refused with a message |
The Almost there screen asks the person to confirm their First name, Last name and E-mail address, accept the privacy policy when your institution has one, and click Create new account. The account is created active and verified, always with the address the provider verified, even if the person edits the email field. Creating an account this way needs self-registration to be on.
Under Already have an account?, Link to an existing account asks for the E-mail address and Password of an existing account. Link existing account signs in with that password and links the provider, so the next sign-in goes straight through. Accounts with two-factor authentication cannot be linked here. The screen must be completed within 15 minutes.
Removing a LinkedIn link
On a person's profile, staff can open the profile's settings, then Miscellaneous, and click Unlink and delete LinkedIn data. This removes the LinkedIn link and any experience entries imported from LinkedIn. Scrubbing or anonymizing a profile does the same.
Full Fabric support sign-in
Full Fabric's own support administrators sign in to your institution through a central Full Fabric Google sign-in. It is separate from your Google provider, needs no setup, adds no button to your login page, and only admits a verified Full Fabric company address that holds an administrator account on your institution.
Common Failures
| What people see | Usual cause | Fix |
|---|---|---|
| "Staff accounts can't sign in with a social account. Please sign in with your email address and password." | A staff or administrator account used Google or LinkedIn | Sign in with email and password or SSO |
| "This Google account is registered to a different email address." | The account for that address is linked to another Google account | Use the linked Google account, or the password |
| "This LinkedIn account is not connected to your account. Continue to get a sign-in link by email." | The address has a passwordless account not linked to this LinkedIn account | Click Continue for an emailed sign-in link |
| "This account has been suspended. Please contact administrative services." | The account is suspended | Contact the institution's administrators |
| "You have not yet verified your account. Please check your mailbox..." | The account's email was never verified | Follow the verification email |
| "We couldn't verify your identity", with technical details such as "You did not grant access to the sign-in provider." or "The sign-in provider did not accept your credentials." | The person cancelled at the provider, or the provider rejected the request (often wrong client credentials or redirect URI) | The page returns after a few seconds; check the provider's credentials and redirect URI |
| On Almost there: "Wrong email or password", "This account uses two-factor authentication and can't be linked here. Please sign in to your account directly." or "Session data missing" | Wrong password, an account with a second factor, or more than 15 minutes on the screen | Retry, sign in directly, or start again from the provider button |
After a provider fails, Continue skips it in that browser for ten minutes: see When a method refuses.
Permissions
Configuring the providers needs core.institutions.institutions_authentication_change. Unlink and delete LinkedIn data needs core.institutions.profile_linked_in_purge. For integration permissions in general, see Integrations.