> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/admin/settings.md).

# Settings

In **Settings**, you tailor Astro to your company: context, enabled tools, access security, and single sign-on.

Here are the available features:

### Company context <a href="#company-context" id="company-context"></a>

Company context is applied to every conversation in the workspace, so Astro's answers reflect how your business works.

To set the context, follow these steps:

1. In the **Company context** section, describe your company, products, customers, and competitors.
2. Click **Save**.

{% hint style="warning" %}
**Important:** don't include passwords, personal data, or confidential information in the context, since it's sent with every conversation.
{% endhint %}

### Usage tools <a href="#usage-tools" id="usage-tools"></a>

In this section, you define which tools each user profile can use.

To set up the tools, follow these steps:

1. In the **Usage tools** section, click the **Profile** selector and choose a profile (e.g., **USER**).
2. Turn tools on or off: **Web search**, **File analysis**, **Code interpreter**, **Memories**, **Experts**, and **Experts Marketplace**.
3. Click **Save**.

{% hint style="info" %}
To allow or block features for a specific team, read [Set usage permissions, in Teams](https://docs.skyone.cloud/english/admin/teams.md).
{% endhint %}

### Security <a href="#security" id="security"></a>

Security options apply to every user in the workspace:

* **Require two-factor authentication (2FA):** users without 2FA will need to set it up the next time they sign in. Sessions that are already open aren't affected.
* **Sign in with email code:** lets users sign in with a code sent by email.

{% hint style="info" %}
The **Sign in with email code** option requires an email service configured on the server. Without it, the option doesn't appear.
{% endhint %}

### Single sign-on (SSO) <a href="#single-sign-on-sso" id="single-sign-on-sso"></a>

With single sign-on, people sign in to Astro through your company's identity provider (IdP).

{% hint style="danger" %}
**Important:** only accounts that already exist in Astro can sign in with SSO. Add users before you turn on single sign-on.
{% endhint %}

#### Set up SSO with OpenID Connect <a href="#set-up-sso-with-openid-connect" id="set-up-sso-with-openid-connect"></a>

To set up single sign-on, follow these steps:

1. Under **Protocol**, select **OpenID Connect**.
2. In the **Issuer URL** field, enter your identity provider's address. Configuration is discovered at `<issuer>/.well-known/openid-configuration`.
3. Enter the **Client ID** generated by your identity provider.
4. Under **Client secret**, click **Change** and enter the client secret.
5. Keep **Use PKCE** on if the client is public, with no secret.
6. Review the **Scope**, **Email claim**, and **Name claim** fields. The defaults are `openid profile email`, `email`, and `name`.
7. Optionally, change the **Button label** (default: **Sign in with corporate login**) and enter a **Button logo URL**.
8. In **Allowed email domains**, enter the accepted domains, separated by commas.
9. Click **Save**.

{% hint style="info" %}
The **Client secret** is stored encrypted and is never shown again. To keep the current secret, leave the field unchanged.
{% endhint %}

{% hint style="info" %}
If **Allowed email domains** is left empty, any domain is accepted.
{% endhint %}

#### Register Astro with your identity provider <a href="#register-astro-with-your-identity-provider" id="register-astro-with-your-identity-provider"></a>

In the **URLs to register with your identity provider** section, copy the values shown and register them in your IdP application before testing the connection:

* **OpenID Connect Redirect URI:** for the OpenID Connect protocol.
* **SAML Assertion Consumer Service (ACS)** and **SAML Entity ID:** for the SAML 2.0 protocol.

Click the copy icon next to each value.

#### Test and turn on SSO <a href="#test-and-turn-on-sso" id="test-and-turn-on-sso"></a>

To turn on single sign-on, follow these steps:

1. Click **Test connection** and wait for the result.
2. Turn on **Enable SSO**. The corporate sign-in button then appears on the sign-in screen.
3. Optionally, turn on **Require SSO for users** so everyone signs in only through single sign-on.

{% hint style="info" %}
**Require SSO for users** is available only after you turn on SSO and complete a successful connection test.
{% endhint %}


---

# 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.skyone.cloud/english/admin/settings.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.
