> 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/sign-in-and-navigation.md).

# Sign in and find your way

Use your organization's Brokvix CRM address and your own operator account. The exact address and sign-in checks are provided by your administrator.

1. Open the Brokvix CRM address supplied by your organization.
2. Complete the sign-in and any additional verification requested for your account.
3. Check the navigation menu for your work area, such as **Clients**, **Marketing**, **Finance**, **Risk**, or **Compliance**.
4. Open the area you need, then use the page heading to confirm that you reached the intended screen.

If you administer multiple tenants or brands, [check the active workspace](/crm-admin/getting-started/active-workspace.md) before continuing. If your expected menu is absent, see [Access and permissions](/crm-admin/getting-started/access-and-permissions.md).

Never share a password, one-time code, or session link with a colleague. Ask your administrator to grant that colleague their own access.


---

# 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/sign-in-and-navigation.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.