server/priv/docs/en/guides/integrations/authentication/sso.md
Tuist offers Single Sign-On (SSO) as a login option to provide additional account security for your organization.
SSO is configured from the Authentication tab in your organization settings. Google and Okta are supported as identity providers.
[!NOTE] SSO controls how members sign in. <.localized_link href="/guides/integrations/authentication/scim">SCIM provisioning</.localized_link> controls whether an identity provider can create, update, and deprovision organization members automatically. For Okta, most organizations configure both.
Google SSO allows any developer who signs in with a Google Workspace account from your domain to be automatically added to your Tuist organization.
[!NOTE] Prerequisites
You need a Google Workspace organization with a verified domain. You must also be authenticated with Google using an email tied to the domain you are setting up.
example.com).Okta SSO uses the OIDC protocol to allow members of your Okta organization to sign in to Tuist.
If you also want Okta to create, update, or deprovision members automatically, configure <.localized_link href="/guides/integrations/authentication/scim#okta">Okta SCIM provisioning</.localized_link> after SSO is working.
Tuist). Optionally upload the Tuist logo.https://tuist.dev/users/auth/okta/callback).your-company.okta.com).https://tuist.dev/users/auth/okta?organization_id=YOUR_ORG_ID).Assign the users or groups that should be allowed to sign in to the Okta OIDC application.
If the same users are also provisioned through SCIM, Tuist links the Okta identity to the existing Tuist user the first time the user signs in through Okta with the same email address.