> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/account-and-security/sso.md).

# SSO and SAML

How sign-in works today, and how to ask about SSO/SAML for your organization.

## How sign-in works today

Primer handles authentication through **email** or a supported **OAuth** provider (for example Google).

## SSO / SAML for your organization

Single sign-on through your own identity provider (Okta, Entra ID, or another SAML/SSO provider) is handled as an **enterprise** arrangement — it isn't a self-serve toggle in Settings. If your organization requires SSO/SAML, contact <support@sayprimer.com> to discuss enabling it for your account.

> SSO/SAML setup is configured by Primer for your organization, not turned on from the app, so there's no self-service SAML screen to fill in. Reach out to support and we'll scope it with you.

Once your team is in, manage who has access and what they can do with [team invitations](/primer/account-and-security/inviting-your-team.md) and [roles and permissions](/primer/account-and-security/roles-and-permissions.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://support.sayprimer.com/primer/account-and-security/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.
