Single sign-on for your company
Let your workspace admin connect your company's identity provider so colleagues sign in with it.
What it does
With single sign-on, colleagues sign in with your company's own identity provider instead of a Tera password. Your workspace's Organization Admin sets it up once; it is part of a full account (see What your access includes). Setting it up needs the details your identity provider issues when you register Tera as an application there.
Connect your identity provider
Open Admin, then Authentication. The SSO Connection tab holds SSO Provider Configuration:
- Copy the Callback URL (ACS) shown at the top and enter it as the redirect URL when you register Tera in your identity provider.
- Enter the Client ID, the Client Secret and the Discovery URL (the provider's OpenID Connect discovery address) from your provider.
- Leave Scopes as filled in unless your provider needs others. The groups scope is what lets Tera read your groups for the mapping step.
- In SSO email domains, list your company's email domains, separated by commas. People who sign in with an address on those domains are sent to your identity provider.
- Choose Save, then Test Connection. It answers Connection successful or Connection failed with the reasons. A note Unsaved changes warns you when you have edited without saving.
- Tick Enabled and save. Switching it off hides the SSO sign-in but keeps your settings.
Map groups to roles
On the Group Mappings tab, enter a Group Name exactly as your identity provider calls it, pick the Role (Viewer, Editor or Organization Admin), add an optional description and choose Add Mapping. People must belong to a mapped group to sign in. Remove Mapping deletes a row. The roles are explained in Invite colleagues and set their roles.
Two options on the SSO Connection tab shape who gets in:
- JIT Provisioning: creates the account automatically the first time someone signs in through SSO.
- Allow unmapped users: lets anyone who authenticates at your identity provider join as a Viewer even without a matching group. It is off by default, and off is the recommended setting.
Require it for everyone
On the Security Policies tab, Enforce SSO requires all users to sign in through SSO and disables password login for the organization. Test the connection first and keep your own sign-in working, then switch it on. Notify members by email sends colleagues a heads-up; ticking the box never emails anyone by itself. The same tab sets Session duration and Idle timeout, and Revoke All Sessions signs everyone out except you.
What your colleagues see
On the sign-in page they enter their work email and are sent to your identity provider. In Overview, their Auth Method shows OIDC and their 2FA Status shows Managed by IdP: two-factor and password rules for them are set in your identity provider, not in Tera. Their account page is described in Sign-in, passkeys and two-factor.