> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/getting-started/deployment-guides/your-first-30-days/4-configure-sso-optional.md).

# 4: Configure SSO (Optional)

Enabling SSO (single sign-on) is a best practice. It isn't required to deploy Material. Without SSO, users sign in through your email tenant.

### Enable SSO

1. From Settings (top toolbar), click **Admin Console**.
2. Toggle **SAML Single Sign-on** to **On**.
3. Copy the **SSO URL** and **Entity ID** from Material then add them to your identity provider. Follow your provider's documentation for more detail.

   <figure><img src="https://content.gitbook.com/content/ksjM8NywYRSHu1IlfxdP/blobs/WnGx28VQ549w0c5VhbJD/image.png" alt="Copy URL and Entity ID from the SAML single sign-on screen" width="375"><figcaption><p>SAML Single Sign-on</p></figcaption></figure>
4. After you provide the SSO URL and Entity ID from step 3 to your identity provider, export the **identity provider (IdP) XML metadata**. It should look something like this:

{% code overflow="wrap" %}

```javascript
<?xml version="1.0" encoding="UTF-8"?><md:EntityDescriptor entityID="http://www.okta.com/xxx" xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"><md:IDPSSODescriptor WantAuthnRequestsSigned="false" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol"><md:KeyDescriptor use="signing"><ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:X509Data><ds:X509Certificate>MII0GCSqGSIb3DQEBCwUAg=</ds:X509Certificate></ds:X509Data></ds:KeyInfo></md:KeyDescriptor><md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</md:NameIDFormat><md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</md:NameIDFormat><md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://your-org.okta.com/app/your_app/exampleAppId/sso/saml"/><md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://your-org.okta.com/app/your_app/exampleAppId/sso/saml"/></md:IDPSSODescriptor></md:EntityDescriptor>
```

{% endcode %}

5. Test your connection. Log out, then log back in. Choose **Sign in with SAML**.
6. Optionally, toggle **Enforce SAML Login**. This requires SSO sign-in for everyone. **Make sure you have tested your connection successfully first**.

{% hint style="info" %}
SAML is also used to allow end users to unlock messages. This is separate from admin login SSO. You'll configure this later in [Deploy Account Takeover Resilience](/getting-started/deployment-guides/deploy-account-takeover-resilience-ator.md).
{% 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.material.security/getting-started/deployment-guides/your-first-30-days/4-configure-sso-optional.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.