> 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 ### 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. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.overleaf.com/commons/single-sign-on-sso/sso-faqs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.