> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/identity-and-access/saml-sso-setup.md).

# SAML SSO Setup

Set up SAML single sign-on with Microsoft Entra ID or Okta, then complete the required We360 support activation.

Set up SAML SSO with your identity provider. Select the guide for your provider.

{% hint style="warning" %}
**Setup is not complete until We360 activates it.** After you configure your identity provider, send its metadata URL to We360 Support. Do not test SSO until Support confirms the configuration is active. Otherwise, sign-in will fail.
{% endhint %}

### Setup flow

1. Create the SAML application in your identity provider.
2. Configure the required SAML values and user assignments.
3. Send the identity provider metadata URL to We360 Support.
4. Wait for Support to confirm activation.
5. Test sign-in through your We360 portal URL.

### Available providers

* [Microsoft Entra ID SAML SSO](https://docs.we360.ai/deployment-and-it-ops/identity-and-access/saml-sso-setup/microsoft-entra-id-saml-sso.md)
* [Okta SAML SSO](https://docs.we360.ai/deployment-and-it-ops/identity-and-access/saml-sso-setup/okta-saml-sso.md)


---

# 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.we360.ai/deployment-and-it-ops/identity-and-access/saml-sso-setup.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.
