> 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/saas-admin.md).

# SaaS Admin

The SaaS Admin works at the platform level and can select an authorized tenant and brand when an operation requires exact brand context. Platform catalogues and tenant or brand lifecycle operations are different from day-to-day client work.

## First checks

1. [Check the active workspace](/crm-admin/getting-started/active-workspace.md). Confirm whether you are in **SaaS Platform** or a specific tenant and brand.
2. Open **SaaS Management** to find **Tenants**, **Brands**, and other platform or brand configuration areas available to you.
3. Before changing anything, verify the intended target and your organization's approval process. A selected brand is not a substitute for approval.

Brand configuration, payment routing, provider settings, and activation can affect live business operations. This first edition does not provide mutation instructions for those screens; task-level guides will be added after QA validation and review.

If a target or option is missing, use [Access and permissions](/crm-admin/getting-started/access-and-permissions.md).


---

# 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/saas-admin.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.