> 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-firms.md).

# Copying across prop firms

Manual copies across different prop firms are allowed after a warning. Automated trading across firms is coming soon.

Prop firms watch for identical trades across accounts. Their rules on copying differ, and breaking them can cost you every account at that firm. TradeSurge reads each firm's policy before it sends a copy.

## Same firm, several accounts

If a firm allows copying between your own accounts, the copy goes through. If a firm forbids it, the leg is refused and the firm's policy is quoted.

## Different firms, one manual order

You can send one manual order to accounts at different firms. Before it is sent, you see a warning about correlated risk: one losing idea now hits several firms at once. The order is sent only after you confirm. Manual trading is your judgment, so TradeSurge warns rather than blocks.

| Name                      | What it means                                                     |
| ------------------------- | ----------------------------------------------------------------- |
| **Manual, same firm**     | Allowed where the firm allows copying. Refused where it does not. |
| **Manual, several firms** | Allowed after a correlated-risk warning and your confirm.         |

## Automated trading across firms

{% hint style="info" %}
**Coming soon.** Automated trading is not live yet. This section describes how it will work.
{% endhint %}

One strategy will be able to run across accounts at different firms. Each firm's copy and bot policy decides each leg. A firm that forbids it is refused, and a firm with an unknown policy gets a warning. A portfolio-wide daily loss limit in R caps the combined loss across every account. When it is hit, new entries pause on every account.

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Autotrade and the promotion ladder</strong></td><td>How strategies will move from demo to live.</td><td><a href="/platform/strategies/autotrade.md">Autotrade and the promotion ladder</a></td></tr><tr><td><strong>Prop-firm directory</strong></td><td>Check a firm's copy and bot policy.</td><td><a href="/free-tools/prop-firm-directory.md">Prop-firm directory</a></td></tr></tbody></table>


---

# 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-firms.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 `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.