> 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/getting-started/active-workspace.md).

# Check your active workspace

**For:** SaaS Admin, Tenant Admin, and Brand Admin.

The active workspace identifies the tenant and brand whose information you are viewing. Check it before making a brand-specific change.

1. Look for the workspace selector in the Brokvix CRM header.
2. Read the selected tenant and brand. A SaaS Admin may also see **SaaS Platform** for platform-level work.
3. If you need a different workspace, choose one of the options available to your account and wait for the application to finish switching.
4. Recheck the header before opening or editing a record.

Tenant Admin options are limited to their tenant; Brand Admin options are limited to their granted brands. Operational roles such as Sales and Finance work in their assigned workspace and do not use this selector. A missing option is not a reason to create a substitute tenant or brand—ask an administrator to verify the scope grant.

See [Access and permissions](/crm-admin/getting-started/access-and-permissions.md) if a workspace cannot be selected.


---

# 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/getting-started/active-workspace.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.