> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-install-administer/user-access-textual/textual-sso.md).

# Single sign-on (SSO)

Tonic Textual respects the access control policy of your single sign-on (SSO) provider. To access Textual, users must be granted access to the Textual application within your SSO provider.

Self-hosted instances can use any of the available SSO options. Textual Cloud organizations can enable Okta SSO.

To enable SSO, you first complete the required configuration in the SSO provider. You then configure Textual to connect to it. For self-hosted instances, you use Textual environment variables for the configuration. For a Textual Cloud organization, you use the **Single Sign-On** tab on the **Permission Settings** page.

After you enable SSO, users can use SSO to create an account in Textual.

For self-hosted instances, to only allow SSO authentication, set the [environment variable](/textual/textual-install-administer/configuring-textual/textual-env-var-configure.md) `REQUIRE_SSO_AUTH` to `true`. For Textual Cloud, this is configured in the application. When SSO is required, Textual disables standard email/password authentication. All account creation and login is handled through your SSO provider. If multi-factor authentication (MFA) is set up with your SSO, then all authentication must go through your provider's MFA.

You can [view the list of SSO groups whose members have logged into Textual](/textual/textual-install-administer/user-access-textual/textual-sso/sso-view-groups.md).

Tonic Textual supports the following SSO providers:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Azure</strong></td><td>Use Azure to enable SSO on Textual.</td><td></td><td><a href="/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-azure.md">Azure</a></td></tr><tr><td><strong>GitHub</strong></td><td>Use GitHub to enable SSO on Textual.</td><td></td><td><a href="/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-github.md">GitHub</a></td></tr><tr><td><strong>Google</strong></td><td>Use Google to enable SSO on Textual.</td><td></td><td><a href="/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-google.md">Google</a></td></tr><tr><td><strong>Keycloak</strong></td><td>Use Keycloak to enable SSO on Textual.</td><td></td><td><a href="/textual/textual-install-administer/user-access-textual/textual-sso/keycloak.md">Keycloak</a></td></tr><tr><td><strong>Okta</strong></td><td>Use Okta to enable SSO on Textual.</td><td>Available for both self-hosted instances and Textual Cloud.</td><td><a href="/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-okta.md">Okta (self-hosted and Cloud)</a></td></tr><tr><td><strong>OpenID Connect (OIDC)</strong></td><td>Use OIDC to enable SSO on Textual.</td><td></td><td><a href="/textual/textual-install-administer/user-access-textual/textual-sso/oidc.md">OpenID Connect (OIDC)</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/textual/textual-install-administer/user-access-textual/textual-sso.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.