> For the complete documentation index, see [llms.txt](https://docs.brokvix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brokvix.com/crm-admin/platform-configuration.md).

# Tenant and brand configuration

Use this area if you are an authorized SaaS, tenant, or brand administrator—or a technology integrator with the same scoped access—configuring how the Admin and Client Portals work for a broker. These are configuration responsibilities, not a shortcut into another tenant's client data.

| Scope           | Start with                                                        | Before a change                                                                        |
| --------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| SaaS platform   | [SaaS Admin](/crm-admin/platform-configuration/saas-admin.md)     | Confirm the owning platform authority and the exact target tenant and brand.           |
| Assigned tenant | [Tenant Admin](/crm-admin/platform-configuration/tenant-admin.md) | Check which brands are in scope and whether the change is a draft or published policy. |
| Assigned brand  | [Brand Admin](/crm-admin/platform-configuration/brand-admin.md)   | Confirm the selected brand, effective configuration, approvers, and review gate.       |

For financial controls, start with [Configure deposit and withdrawal approvals](/crm-admin/platform-configuration/configure-financial-approval-flows.md). Its [transaction-to-decision map](/crm-admin/platform-configuration/configure-financial-approval-flows/from-transaction-to-decision.md) separates a workflow's rule and fallback from the no-workflow authoritative route. Publishing an overlapping workflow can change live routing; test the exact brand and initiator channels before publication.

Client-facing instructions belong in the [Client Portal](/crm-client.md). Endpoint contracts for external integrations belong in the [REST API reference](/rest-api.md), not in these configuration guides.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brokvix.com/crm-admin/platform-configuration.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 `build a script that syncs our docs to a CMS` 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.