> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/others/setting-up-sso.md).

# Setting up SSO

Configure SSO for Drivetrain to streamline team access and enforce identity provider auth. Covers SAML setup and IdP configuration.

This guide covers setting up Single Sign On (SSO) for logging into the Drivetrain application with SAML.

Drivetrain works with any SAML identity provider, including Microsoft Entra ID (Azure), Okta, Google, OneLogin, JumpCloud and AWS.

Before proceeding, verify your subscription plan or check with your Customer Success Manager.

Please follow the steps below to configure SSO for Drivetrain.

{% stepper %}
{% step %}

### Create a SAML Application

In your SSO Provider’s console, create a SAML Application with following settings:

**Application name**: Drivetrain

**Single sign-on URL** (also called ACS URL or Reply URL): [https://id.drivetrain.ai/drive/saml/config/default/\<yourDrivetrainSubdomain>](https://id.drivetrain.ai/drive/saml/config/default/)

{% hint style="info" %}
EU customers use a different domain: [https://id.eu.drivetrain.ai/drive/saml/config/default/\<yourDrivetrainSubdomain>](https://id.eu.drivetrain.ai/drive/saml/config/default/)
{% endhint %}

The *yourDrivetrainSubdomain* above is the subdomain of the URL you use to login to Drivetrain.

For example, for "**journey**.drivetrain.ai", subdomain is "**journey**" and the SSO URL is: <https://id.drivetrain.ai/drive/saml/config/default/journey> (EU customers: <https://id.eu.drivetrain.ai/drive/saml/config/default/journey>)

**Audience URI**: [https://app.drivetrain.ai](https://app.drivetrain.ai/)

**Name ID format**: EmailAddress. The Name ID must be the user's Drivetrain login email.

Finish creating the application.
{% endstep %}

{% step %}

### Share application metadata

Once your application is created, please share:

* **Metadata** file of the new application
* **The embed URL** of the application with your Drivetrain customer success manager. This is the URL that will be shown when a user will go to yourDrivetrainsubdomain.drivetrain.ai and click on the “Sign in with SSO” button<br>

  <figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-5131874a20d6662ccec92b5152a550508d5b2ff9%2Fsetting-up-sso-01.png?alt=media" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Assign users in your SSO Provider

In your SSO provider, assign the 'Drivetrain application' you created above to your users who will be using the application.
{% endstep %}

{% step %}

### Configure roles in Drivetrain

Drivetrain doesn't create users when they first sign in with SSO: a user who isn't in your Drivetrain workspace can't sign in. These users will additionally need to be added on the Drivetrain app with the appropriate [Role Based Access Control](https://github.com/DrivetrainAi/gitbook-integrations/tree/main/en/user-administration-and-access/access-control-and-permissions/README.md) configuration in place to be able to access boards, models and metrics.

If you’re an admin on Drivetrain, you will be able to configure roles by heading over to **Settings > Users** (to add or remove users) and **Settings > Roles** (to manage user permissions).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For any additional queries, please reach out to your Drivetrain Customer Success Manager, or email us at <support@drivetrain.ai>
{% endhint %}

## FAQ

<details>

<summary>Does Drivetrain support SSO?</summary>

Yes. Drivetrain supports SAML single sign-on with all major identity providers, including Microsoft Entra ID (Azure), Okta, Google, OneLogin, JumpCloud, and AWS. Verify your subscription plan or check with your Customer Success Manager before configuring SSO.

</details>

<details>

<summary>A user clicks Sign in with SSO and lands back on the Drivetrain login page. Why?</summary>

Drivetrain shows no error message when an SSO sign-in fails. Check that:

* the user is assigned to the Drivetrain application in your SSO provider
* the Name ID your SSO provider sends is the user's Drivetrain login email
* the user's email domain is one of your workspace's SSO domains, if any are set
* the signing certificate Drivetrain has matches the one your SSO provider uses (for example, after a certificate rotation)

</details>

<details>

<summary>A user signs in with SSO but can't access Drivetrain. Why?</summary>

The user isn't in your Drivetrain workspace yet. An admin needs to add them under **Settings > Users**.

</details>


---

# 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://integrations.drivetrain.ai/integration-guide/readme/others/setting-up-sso.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.
