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

# Register and sign in

Use the Client Portal address supplied by your broker. Another broker's portal may look similar but will not be the right place for your account.

1. If you are new, choose **Sign up** or **Register** when your broker offers it. Complete the information and verification steps shown for your account type; the available registration journey can differ by broker.
2. If you already have an account, choose **Sign in** and use your own credentials. Complete any requested security check privately.
3. Once signed in, check your account and available menu. Continue with [account verification](/crm-client/account-verification.md) if the portal requests it before funding or trading.

If registration is not offered or you cannot sign in, contact your broker through an official support channel. Do not share a password, one-time code, or sign-in link. The [portal orientation](/crm-client/getting-started.md) explains where to find the main areas after sign-in.


---

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