> 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/trading.md). # Trading Sign in to your broker's Client Portal and open **Trade** when it is available for your account. The trading workspace may show a market watch, chart, order entry, and your open positions. Select the intended trading account and symbol before reviewing a quote or placing an order. Check the order type, buy or sell side, volume, displayed price, and any stop-loss or take-profit values on the confirmation screen. Market prices can change; a chart or quote is not a guarantee of execution price. If the expected account, symbol, or trading permission is missing, contact your broker rather than placing an order in another account. For funding and transaction status, use [Deposits, withdrawals, and history](/crm-client/funds-and-history.md). This guide helps you find the workspace; it does not recommend a trade or strategy. --- # 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/trading.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.