> 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.14/learn-about-mult-tenant/plan-your-multi-tenant-deployment/saml-for-multi-tenant-deployments.md).

# SAML for Multi-Tenant Deployments

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.

If you need to provide User A access to the main account and tenant account, and User B access to only a tenant account, we recommend configuring one SAML integration on the main account (do not propagate to tenants) and a separate SAML integration on the tenant account. User A receives the URL for the main account and can access both main and tenant account. User B receives the URL for the tenant account and does not have access to main. If we want User C to also have access to only the tenant account, but with more limited permissions, we can configure the SAML integration on the tenant to restrict User C to the default analyst role or a custom role we create.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.14/learn-about-mult-tenant/plan-your-multi-tenant-deployment/saml-for-multi-tenant-deployments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.