> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/accounts/manage-accounts.md).
# Manage your accounts
Watch each account's rules, compliance history and key status from its account page.
Once an account is added, its page is where you check it and adjust it. Each account page has three tabs: Overview, Rules & Limits and Compliance. This page explains what each tab is for.
## Overview shows the account at a glance
Overview shows the account's firm, phase, size, risk dial and status. If no key is registered, this is where you register one.
## Rules & Limits shows how close you are to each limit
Every firm limit appears as a progress bar: daily drawdown, maximum drawdown, profit target and consistency where the firm has one. A limit the catalogue has not confirmed is marked **Limit unconfirmed**. TradeSurge blocks new entries on that account rather than trade against an unknown rule.
## Compliance shows what was blocked and why
Compliance is the account's breach history. Every entry that was blocked, and every Breach Guard action, is recorded with its reason.
## Tighten Breach Guard per account
On Rules & Limits you can set the **safety margin**, the point at which Breach Guard acts. The default is 90% of each firm limit. You can tighten it as low as 50%, but never widen it past the firm limit.
{% hint style="warning" %}
If an account shows "Limit unconfirmed", do not assume it is safe to trade. New entries on that account stay blocked until the firm's limit is confirmed.
{% endhint %}
## Good to know
* The risk dial is set per account, so the same trade can risk a different amount on each one.
* A Terminal account stays read-only until its key is on the engine.
## Next steps
---
# 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://docs.tradesurge.co/platform/accounts/manage-accounts.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.