Single sign-on (SSO)
With single sign-on, people at your company sign in to linkable.id with their company account: Microsoft Entra ID, Okta or Google Workspace. Your identity provider handles the password, MFA and offboarding, and linkable.id trusts it.
Availability: the Enterprise plan. linkable.id support sets it up with your IT team (see For your IT team).
Signing in
- On the sign-in page, enter your work email and choose Continue.
- If your email is on one of your company's domains, choose Continue with your identity provider (for example Continue with Microsoft Entra ID).
- Sign in with your company account. You come back to linkable.id, signed in.
People whose email isn't on your company's domains, like an agency or a consultant, keep signing in with their email and password, and the account's two-factor rule applies to them.
Your first sign-in
- You already have a linkable.id user: the first time you sign in with SSO, your company account is linked to it by your email. From then on, linkable.id recognizes you by your company account, even if your email changes there.
- You don't have a user yet: depending on how your account is set up, linkable.id either creates one for you in a default workspace and role (a super admin can change them afterwards), or asks you to contact an administrator.
Two-factor sign-in
If your identity provider requires MFA for everyone, and your administrator confirmed this when setting up SSO, signing in with SSO counts as two-factor: linkable.id doesn't ask for a second factor of its own. Otherwise, the account's two-factor rule applies on top of SSO.
Once SSO is also required for your domains (see below), people on those domains can only sign in through your identity provider, so the two-factor rule doesn't send them reminders to set up a second factor, and Users shows Single sign-on in their Two-factor column. Two exceptions:
- Claude connections and API tokens still need an authenticator app or passkey of the person's own once the rule is enforced: a token can't show how it was approved. People who have one keep getting the reminders.
- Break-glass accounts keep password sign-in, so they need an authenticator app or passkey of their own too.
When SSO is required
Once everyone has tried SSO, linkable.id support can require it for your company's domains:
- People on those domains can only sign in with SSO. Password sign-in, passkeys and password reset stop for them, and anyone signed in another way is asked to sign in again.
- Up to three break-glass accounts (usually your super admins) keep password sign-in, for when the identity provider is unavailable. They need their own authenticator app or passkey, and every time one is used, the other super admins get an email.
- Optionally, the account can also be closed to emails outside your domains: then nobody else can sign in, and no user can be created with such an email.
Disabling someone in your identity provider stops their sign-in to linkable.id. With directory sync (Microsoft Entra ID and Okta), they're also suspended here at once, which stops their API tokens and Claude connections. Without it, those keep working until a super admin suspends or removes the user in Users, so suspend people who leave.
For your IT team
linkable.id uses OpenID Connect. Register linkable.id as a web application in your identity provider with:
- Redirect (callback) URL:
https://your-admin-domain/sso/callback, where your-admin-domain is the address where you sign in to linkable.id. Support confirms the exact URL. - Scopes:
openid,email,profile. - Who can sign in: only your organization's accounts.
Then send linkable.id support, through a secure channel (never plain email for the secret):
- The issuer:
- Microsoft Entra ID:
https://login.microsoftonline.com/{your-tenant-id}/v2.0, with your directory (tenant) ID. The sharedcommonandorganizationsendpoints aren't accepted. - Okta: your Okta org's issuer, for example
https://your-org.okta.com. - Google Workspace:
https://accounts.google.com, with an OAuth client of type Web application whose consent screen is limited to your organization (Internal). linkable.id only accepts accounts of your Workspace domains.
- Microsoft Entra ID:
- The client ID and client secret.
- Your company's email domains.
- Whether your sign-in policy requires MFA for everyone.
Menu names in the admin consoles change over time; the values above are what matters.
If something goes wrong
- "Single sign-on didn't complete": try again. If it keeps happening, ask your administrator; the identity provider may have refused the sign-in.
- "Your company account can't sign in to linkable.id yet": you have no linkable.id user and the account doesn't create one automatically. Ask a super admin to add you.
- "Your account now signs in with single sign-on": SSO was just required for your domain. Sign in again with Continue with your identity provider.
With Claude
Claude can't manage single sign-on yet: that stays in the panel.