> 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-end-customers.md).

# SSO — End Customers

Enable brand-managed SSO for customer login across Reach-powered web and app experiences.

### Overview

**End-customer SSO** lets customers log in to **Reach-powered experiences** using **brand-managed credentials**.

Reach delegates authentication to your **Identity Provider (IdP)**. Reach does **not** store passwords.

{% hint style="info" %}
Need SSO for Reach Central users? See [SSO — Agents](/customizations-and-bolt-ons/bolt-ons-catalog/sso-agents.md).
{% endhint %}

<a href="https://datami.atlassian.net/helpcenter/Boltons/portal/1488/group/1848/create/2353" class="button primary" data-icon="cart-shopping">Buy this bolt-on</a>

* **What it is:** Brand-managed SSO for customer login.
* **What problem it addresses:** Eliminates duplicate accounts and centralizes security policies.
* **Who it is intended for:** Customers using Reach-powered web and app experiences.

### Typical use cases

* Let customers reuse an existing **brand login**
* Reduce friction in **checkout** and **self-care**
* Centralize **MFA** and **security policy** under the brand

### Scope

* **What is included:**
  * **SSO integration** for customer login across Reach-powered surfaces:
    * brand website
    * mobile web
    * mobile apps
    * checkout and self-care portals
  * **Session creation** and **identity linkage**
* **What is excluded:**
  * **Agent SSO** for Reach Central
  * **Brand password reset** and **credential management**
  * Customer **identity merges** or **migrations**

### Brand inputs

* Which **IdP** will be used and who owns it
* Which **identity fields** will be used to match customers
* A small set of **test customers** for validation
* **Approval owner** for go-live

### Requesting this bolt-on

For the standard request 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-end-customers)

### Frequently asked questions

#### When should we request end-customer SSO?

Request it when your brand identity system is ready for integration.

#### What happens after we purchase?

Reach confirms the scope and collects your IdP details.

<a href="https://datami.atlassian.net/helpcenter/Boltons/portal/1488/group/1848/create/2353" class="button primary" data-icon="cart-shopping">Buy this bolt-on</a>

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> 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-end-customers.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.
