> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/sso-agents.md). # SSO — Agents Enable brand-managed SSO for agent access to Reach Central via your Identity Provider (IdP). ### Overview **Agent SSO** lets internal users log in to **Reach Central** using credentials managed by your organization. Reach delegates authentication to your **Identity Provider (IdP)**. Reach does **not** store **agent passwords**. {% hint style="info" %} This covers agent access to Reach Central only. Customer SSO is handled separately. {% endhint %} Buy this bolt-on * **What it is:** Brand-managed SSO for Reach Central users. * **What problem it addresses:** Centralizes access control, MFA, and deprovisioning in your IdP. * **Who it is intended for:** Brand care, sales, operations, and admin users of Reach Central. ### Typical use cases * Use existing **corporate login** for Reach Central * Enforce brand **MFA policies** for agent access * Simplify **onboarding** and **offboarding** of agents ### Scope * **What is included:** * **SSO integration** for Reach Central agent login * Basic **identity attribute mapping** * **Session creation** and **agent attribution** in audit logs * **What is excluded:** * **Customer SSO** * **Authorization decisions** made by your IdP * Automatic permissioning in Reach Central based on **IdP groups** ### Brand inputs * Which **IdP** will be used and who owns it * Which **identity fields** Reach Central should use * A small set of **test users** for validation * **Approval owner** for go-live ### Requesting this bolt-on For the standard process, commercial notes, and support, see [Bolt-ons catalog](/customizations-and-bolt-ons/bolt-ons-catalog.md). ### Technical details For the implementation-specific setup details, visit: [SSO technical details](https://reachplatform.gitbook.io/reachplatform-docs/technical/~/revisions/b3C3M4tkkLMyqmMcGAsL/bolt-on-setup/sso-agents) ### Frequently asked questions #### When should we request agent SSO? Request it when your brand IdP is ready for Reach Central integration. #### What happens after we purchase? Reach confirms the scope and collects your IdP details. Buy this bolt-on {% hint style="info" %} Questions or clarification? Reach out to your respective account manager or email us at for help and support. {% endhint %} --- # 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.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/sso-agents.md?ask=&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.