> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.15/learn-about-mult-tenant/plan-your-multi-tenant-deployment/saml-for-multi-tenant-deployments.md).

# SAML for Multi-Tenant Deployments

Configure SAML 2.0 authentication for main and tenant accounts in a Cortex XSOAR 6.15 multi-tenant deployment.

You can authenticate your Cortex XSOAR users using SAML 2.0 authentication with your identity provider, such as Okta. You need to define Cortex XSOAR authentication in your Identity Provider’s account, then create a SAML 2.0 instance in Cortex XSOAR. In some cases, you may need to provide some users with access to the main account and other users access only to a tenant account. You can do this by configuring SAML separately for the main account and for the tenant account.

To give users different access levels, configure separate SAML integrations:

* Configure a SAML integration for the main account. Do not propagate it to tenants.
* Configure a separate SAML integration for each tenant account.

Give users the URL for the account they need to access:

* User A receives the main account URL. They can access the main and tenant accounts.
* User B receives a tenant account URL. They cannot access the main account.
* User C receives a tenant account URL. Restrict their access to the default analyst role or a custom role.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.15/learn-about-mult-tenant/plan-your-multi-tenant-deployment/saml-for-multi-tenant-deployments.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.