> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/administration/sso-saml2.0.md).

# SSO SAML2.0

SSO SAML2.0 Instructions for Currents

Currents supports SSO integration via SAML 2.0, including JIT provisioning and SCIMv2. When enabled, authentication will be deferred to your Identity Provider (IdP).

[Setting Up SSO](/dashboard/administration/sso-saml2.0/setting-up-sso.md) walks through the request from the dashboard. Follow the instructions for your IdP alongside it:

* Setup with [Azure AD / Entra ID](/dashboard/administration/sso-saml2.0/azure-ad.md)
* Setup with [Okta](/dashboard/administration/sso-saml2.0/okta.md)
* Setup with [JumpCloud](/dashboard/administration/sso-saml2.0/jumpcloud.md)
* Manual [SAML2.0 Configuration](/dashboard/administration/sso-saml2.0/saml2.0-configuration.md)

### Before you start

* SSO is part of the Business and Enterprise plans.
* Once SSO is on, people with an email on your listed domains sign in through your IdP. They can't use a password or social sign-in for Currents.
* Users are created the first time they sign in. Add [SCIM User Provisioning](/dashboard/administration/sso-saml2.0/scim-user-provisioning.md) if you also want your IdP to create and remove users.
* To open Currents from your IdP's app list, see [IdP-initiated Sessions](/dashboard/administration/sso-saml2.0/idp-initiated-sessions.md).

### Troubleshooting

See [Troubleshooting SSO](/dashboard/administration/sso-saml2.0/troubleshooting-sso.md) section for help.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/dashboard/administration/sso-saml2.0.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 `build a script that syncs our docs to a CMS` 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.