> 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/access-and-permissions.md).

# Understand missing menus and access

The CRM menu is not identical for every user. A screen or action can depend on your role, assigned permissions, active tenant or brand, and whether the relevant module is enabled.

If you cannot find an expected screen:

1. Confirm you are signed in with your own operator account.
2. If you have a workspace selector, confirm the [active workspace](/crm-admin/getting-started/active-workspace.md).
3. Search the navigation area named in the guide; some items are nested under a parent menu.
4. Ask your administrator to check your role, permissions, workspace scope, and module availability. Include the page name and the time of the issue, but never send a password or session token.

A visible menu item does not guarantee that every action on the page is allowed. If an action is denied, do not retry using a different person's account; request the correct access through your organization's process.


---

# 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/access-and-permissions.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.