> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/commons/single-sign-on-sso/sso-faqs.md).

# SSO FAQs

Frequently asked questions about Commons single sign-on.

### Do you support SCIM?

System for Cross-domain Identity Management (SCIM), is a standard for automation of user provisioning. Because your system will not be provisioning users in Overleaf, SCIM is neither supported nor required. Individual users own their Overleaf accounts, these may be provisioned by the users before joining the subscription and can be retained by them after they leave.

### Do you support Just in Time (JIT) Provisioning of user accounts?

Yes. If a user signs in via SSO and their SSO identifier does not match one in our system they can either (a) provision a new account or (b) identify an existing account under a different email that should be associated with the SSO identity.

### Do you support IDP initiated authentication flows?

No, Overleaf only directly supports SP initiated flows for authentication. We do provide a url that may be provided to your users that can simulate an IDP initiated flow.

### What do you do with the SAML attributes sent in the authentication response?

Overleaf reads the SAML attributes agreed with your IT services team during setup. These include the user's SSO identifier and institutional email address. We may also use optional first and last name attributes to initialize account details, and an entitlement attribute to determine subscription eligibility.

Other SAML attributes are not associated with the account, stored against the user, or used for other purposes. This includes attributes such as role or department. See [Your Admin Hub](https://docs.overleaf.com/commons/user-management/your-admin-hub.md) for where that information comes from.


---

# 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.overleaf.com/commons/single-sign-on-sso/sso-faqs.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.
