> 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/textual-sso-okta/textual-configuration-textual-cloud.md).

# Textual configuration (Textual Cloud)

{% hint style="info" %}
**Required global permission:** Manage users and groups
{% endhint %}

On Textual Cloud, after you [complete the configuration in Okta](/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-okta/okta-configuration.md), you configure the Textual connection to Okta from the **Single Sign-On** tab on the **Permission Settings** page.

The Textual configuration requires some values from the configuration in Okta. For more information, go to [Okta configuration](/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-okta/okta-configuration.md#getting-the-required-values-for-the-textual-configuration).

1. To enable Okta SSO, check the **Enable Okta SSO** checkbox.
2. In the **SSO Client ID** field, enter the client identifier of the application.
3. In the **SSO Domain** field, enter the Okta domain.
4. If you use a third-party provider, then in the **Identity Provider ID** field, provide the provider identifier.\
   \
   If you do not use a third-party provider, then you can skip this field.
5.  If you created a custom authorization server, then in the **Authorization Server** field, provide the server identifier.\
   \
   If you did not create a custom authorization server, then you can skip this field.
6. To use the Okta PKCE authorization flow, check **Use PKCE flow**.\
   \
   Make sure that your Okta configuration uses the **Authorization Flow** and **Refresh Token** grant types.
7. To require your organization users to use Okta SSO to log in to Textual, check the **Require SSO for login** checkbox.


---

# 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/textual-sso-okta/textual-configuration-textual-cloud.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.