> 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.md). # Admin Portal The Admin Portal serves two groups: broker teams managing clients and authorized technology or platform administrators configuring tenants and brands. Choose your work area first; both use the same portal but may see different menus and permissions. ## Start here * [Broker teams](/crm-admin/broker-teams.md) — Sales, Marketing, Finance, Risk, Support, and Compliance work with client records and requests. * [Tenant and brand configuration](/crm-admin/platform-configuration.md) — SaaS, tenant, and brand administrators and authorized technology integrators manage the platform configuration they are permitted to change. * [Get oriented in the Admin Portal](/crm-admin/getting-started.md) — sign in, check the active workspace, and understand missing menus. ## What to expect The screens and actions you see depend on your permissions, active tenant or brand, and enabled modules. Each task guide explains where to work and what to check; it does not grant authority to change another brand's configuration. If a menu is missing, ask an administrator to review your access rather than using someone else's account. If you are handling a live client request, follow your organization's approval and escalation policy. Admin Portal guidance is not for clients using a broker-branded [Client Portal](/crm-client.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.md?ask=&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.