> 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/terminal/copy-across-accounts.md).
# Copy a trade across accounts
One manual order is copied to every selected account, sized from each account's own risk dial.
Copying is not a separate tool in TradeSurge. The Terminal is the copier: every order you place goes to all the accounts you select. Each copy is sized for its own account, so one idea becomes a consistent position across your whole book.
## Each account is sized on its own
TradeSurge does not copy a quantity. It copies the idea and the stop, then sizes each leg from that account's balance and risk dial. The result is the same R on every account, whatever the account size.
## Each leg is checked on its own
Every leg passes the same checks as a single trade: firm rules, Breach Guard, caps and pre-send checks. A refused leg never stops the others.
| Name | What it means |
| -------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Allowed** | The leg passes every check and is sent. |
| **Refused by firm policy** | The firm does not allow copying between accounts, so TradeSurge will not send it. The firm's policy is quoted. |
| **Unknown copy policy** | The firm's copy rule is not in the catalogue yet. You see a warning before you confirm. |
| **Correlated flow** | The selection spans more than one firm. You see a warning before you confirm. |
## There is a cap on accounts per order
One order can go to up to 10 accounts by default. The cap keeps one tap from turning into more commands than the exchange will accept.
{% hint style="info" %}
The warnings in the Terminal are there so you see a refusal before you submit. The engine enforces the same rules again on its side, so skipping the warning changes nothing.
{% endhint %}
## 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/terminal/copy-across-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.