> For the complete documentation index, see [llms.txt](https://help.quantower.com/quantower/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.quantower.com/quantower/informational-panels/account-info.md).
# Account info
View all your trading account details in the Quantower Account Info panel — balances, margin, and key metrics, plus the option to lock trading per account
The purpose of this panel is to show all of the available account information to the user. Account info panel is required to have at least one active connection with a trading account to show data about.
The set of parameters varies depending on a particular account (Connection) and represents the total list of all data provided by the vendor.
{% hint style="success" %}
You can hide the toolbar containing the "**Account lookup**" field (via Settings) in case you have only one connection in order to save some space.
{% endhint %}
To open a new Account info panel, go to the ***Main menu*** (Logo icon) and select ***Account info (ACC)*** in the Information section.
## **Lock Trading for the Selected Account**
This option allows you to manually lock a selected account, preventing any trading operations from being executed on the wrong account.
Lock Trading for the Selected Account
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.quantower.com/quantower/informational-panels/account-info.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 `automate deployments from our CI pipeline` 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.
