Skip to content

Single sign-on (SSO)

Let your team sign in with Okta, Microsoft Entra ID, Google Workspace or any SAML 2.0 or OpenID Connect identity provider.

Available on EnterpriseUpdated 4 min read
On this page
  1. Step 1: Verify your email domains
  2. Step 2: Connect your identity provider
  3. Step 3: Sign-in rules
  4. How your team signs in
  5. Recent SSO activity
  6. Removing a domain or changing plan

With single sign-on, your team signs in with your company's identity provider, so joiners and leavers are handled where you already manage them. Single sign-on is part of the Enterprise plan, and only the organisation owner can set it up.

To open it, click your picture at the bottom of the rail, select Agency branding, then Single sign-on. Setting it up has three steps.

Step 1: Verify your email domains

Only people whose email address is on a domain you have verified can sign in through your identity provider.

  1. Under Verify your email domains, enter your Email domain, such as northwind.com, and select Add domain.
  2. Add the TXT record shown where that domain's DNS is managed. If your DNS provider asks for a name, use @ (the domain itself).
  3. Select Check. When Trabbly finds the record, the domain shows Verified. You can leave the TXT record in place.

DNS changes can take a while to appear. If the check fails, it tells you why; try again later.

Step 2: Connect your identity provider

First create an app for Trabbly in your identity provider. Then, under Connect your identity provider, choose the Protocol.

OpenID Connect

  1. Give your identity provider the Sign-in redirect URI shown (select the copy button). Use the authorisation code flow with the scopes openid, email and profile. Trabbly adds PKCE itself.
  2. Enter the Issuer URL, for example https://northwind.okta.com, https://login.microsoftonline.com/<tenant ID>/v2.0 or https://accounts.google.com.
  3. Enter the Client ID and Client secret. The secret is stored encrypted and never shown again; leave it blank later to keep it.

SAML 2.0

  1. Give your identity provider the Entity ID (audience) and ACS URL (reply URL) shown. After saving once with SAML selected, you can also Download our SAML metadata.
  2. Ask your provider to send the email address as the NameID or an "email" attribute, and to sign the assertion.
  3. Add your provider's details in one of three ways: Metadata URL (we download it when you save), Paste metadata, or Enter by hand (the identity provider entity ID, the HTTP-Redirect sign-in URL and the signing certificate in PEM format).

Once a certificate is stored, the page shows the current provider and when its certificate expires.

Step 3: Sign-in rules

Setting What it does
Turn on single sign-on Shows your provider to people on your verified domains when they choose Sign in with SSO. Passwords keep working unless you require SSO.
Require single sign-on Members on a verified domain can only sign in through your provider. Needs a verified domain.
Create accounts automatically Someone on a verified domain who signs in through your provider but has no Trabbly account yet gets one. They cannot see any brand until an admin gives them access.
Role for new accounts Member (sees only the brands an admin adds them to) or Admin (sees every brand and manages the team). Choose Admin only if everyone in your provider's app should be an admin.

Select Save single sign-on.

People who sign in with single sign-on skip Trabbly's own two-factor step, so set up multi-factor authentication in your identity provider. Accounts created automatically count towards your team member limit; if there is no free seat, the sign-in is refused.

How your team signs in

On the sign-in page, people select Sign in with SSO, enter their Work email, and are sent to your identity provider's sign-in page. If something goes wrong, the sign-in page explains it, for example "Your email domain is not verified for single sign-on in this organisation" or "Your organisation has no free team seats".

Recent SSO activity

The Recent SSO activity panel shows the last ten single sign-on events: successful sign-ins (and new accounts), failed sign-ins with the reason, and owners using their password while SSO is required. All of these are also in the activity log.

Removing a domain or changing plan

  • Removing a verified domain sends the people on it back to their passwords. If no verified domain is left, Require single sign-on switches off.
  • If you move off Enterprise, single sign-on stops and everyone signs in with their email and password.

Was this article helpful?

Ask a question