> 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/faqs/general/platform-and-integrations-faq.md).

# Platform & Integrations FAQ

Shared responsibility model, third-party integrations, and ownership.

### Quick answers

<details>

<summary>Which third-party integrations are available out of the box?</summary>

Reach Common includes standard integration patterns across common categories.

Specific vendors are selected by the brand.

Common categories include:

* Identity & Access (SAML 2.0 SSO for customers and agents, when contracted)
* payment gateways
* financing providers
* tax calculation engines
* device support and knowledge platforms
* analytics and affiliate tracking (via GTM)
* email and SMS providers
* logistics and fulfillment partners
* reporting, dashboards, and data exports

Reach provides the integration framework.

Vendor selection and commercial agreements remain brand-owned.

</details>

<details>

<summary>What does Reach do vs what does the partner/brand do?</summary>

Reach responsibilities typically include:

* platform hosting and maintenance
* checkout, cart, pricing, and promo engine
* secure sessions after authentication
* order orchestration and transaction processing
* reporting, dashboards, and audit trails
* API layer and third-party integrations
* role-based access and agent attribution

Partner / brand responsibilities typically include:

* Identity Provider (SSO), if used
* payment gateway and financing contracts, if used
* tax configuration and compliance decisions
* pricing, promotions, and offers
* branding, content, and UX approvals
* regulatory and legal compliance
* downstream billing and invoicing systems

</details>

<details>

<summary>How do we maintain security and compliance?</summary>

Security follows a shared responsibility model.

Identity & access:

* SAML 2.0 SSO can be enabled (when contracted)
* the brand controls passwords, MFA, and account policies in its Identity Provider
* Reach does not store user credentials

Platform controls:

* signed auth tokens
* session expiry and re-authentication
* role-based access control (RBAC)
* agent attribution for actions in Reach Central

Auditability:

* audit trails for key actions
* transaction and activity logging
* separation of customer vs agent access

Regulatory compliance and data governance are owned by the brand.

</details>


---

# 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/faqs/general/platform-and-integrations-faq.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.