An SSO sign-in entry exists for organizations with a configured identity connection. Self-service provider-connection setup, domain administration, and a verified SCIM rollout are not released workflows. Sign-in availability depends on the deployment’s organization and provider configuration.
Sign in to a configured organization
Use this flow only when your administrator has confirmed that the organization is configured.1
Open SSO sign-in
Open Continue with SSO, enter your company address in Email, and select Continue.
2
Follow the configured provider flow
The application looks up an organization using the email domain and starts authorization. If no matching workspace is found, ask the administrator to verify the domain and organization mapping.
3
Confirm workspace access
After a successful sign-in, confirm the selected workspace and available resources. A successful identity-provider login alone does not establish every workspace permission.
Prepare provider and SCIM setup
Use the focused preparation guides for Microsoft Entra SAML SSO, Okta SAML SSO, and SCIM.
Existing directory-related fields or badges do not prove that provisioning and deprovisioning work end to end. Obtain supported setup instructions through the Help Center and verify the complete lifecycle before enforcing a new sign-in policy.
Is SSO the same as SCIM?
Is SSO the same as SCIM?
No. SSO handles authentication; SCIM concerns directory provisioning. Each needs a separately supported and verified setup.
Can I enforce SSO from this page?
Can I enforce SSO from this page?
No self-service enforcement control is documented. Do not infer enforcement from the presence of a sign-in form.
Which provider metadata should I paste into Threetone?
Which provider metadata should I paste into Threetone?
Wait for the supported connection instructions for your organization. Do not guess entity IDs, redirect URLs, certificates, or provisioning tokens.