> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/admin-manage-your-brokerages-apps-and-sso.md).

# Admin: Manage Your Brokerage’s Apps & SSO

Brokerage Admins can now manage My Apps and SSO connections directly in Rechat. Configure, update, and control your app ecosystem without relying on support or engineering.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FrHJ4mlrMQpVdpZxi0t2T%2FSSO_My%20Apps.jpg?alt=media&amp;token=f369a322-5c43-4ef0-9e87-e425d5503f15" alt=""><figcaption></figcaption></figure>

#### **Take Control of Your Brokerage’s App Ecosystem**

You can now manage your brokerage’s **My Apps and SSO (Single Sign-On) connections directly inside Rechat**.

No more waiting on support or engineering—everything you need to configure and maintain SSO is now available in your Admin settings.

#### **Why This Matters**

⚡ **Move Faster:** Set up and update integrations on your own timeline

🔐 **Improve Security & Access Control:** Centralize login access across your brokerage’s tools

🧩 **Simplify Your Tech Stack:** Give agents a seamless login experience across platforms

#### **What’s Included**

* Self-service **SAML SSO configuration (IdP mode)**
* Full control over **My Apps**
* Certificate and metadata management
* App ordering and visibility controls

#### **Who This Is For**

This feature is designed for:

* Brokerage Admins
* Marketing/Admin leaders
* IT teams or technical partners

{% hint style="info" %}

#### **Important Note**

This release supports **Rechat as the Identity Provider (IdP)**—allowing your agents to log into other tools. Support for managing SSO where Rechat acts as a Service Provider (SP) will be added in a future release.
{% 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://help.rechat.com/whats-new/admin-manage-your-brokerages-apps-and-sso.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.