A firm can permit automated software while restricting the origin of its trading decisions. It can also treat copying between your own accounts differently from following somebody else's signal channel. “EAs allowed” therefore does not settle whether a particular Telegram route is permitted.
Read the terms for the exact programme, account stage and product you intend to use. Evaluation, funded and futures programmes may have different conditions, even under one brand. Keep the dated source and obtain clarification from the firm when the proposed workflow is not clearly covered.
In this guide
Describe the workflow precisely
A useful compliance question names who generates the decisions, which accounts receive them and whether another person controls execution. Say whether the source is your own private channel, a third-party subscription or a shared strategy. Calling all three “automation” removes precisely the distinction that the firm may care about.
Also describe the execution environment: an MT5 EA, an API connection or another approved platform route. The MT5 guide and Tradovate guide cover different technical requirements. Platform support does not imply programme permission.
Do not carry a rule between programmes
As a concrete example checked on 29 September 2026, FTMO's futures prohibited-practices page prohibits copying third-party trading decisions, including signal services, into its Evaluation and Sim-Funded accounts. That is a programme-specific source, not a statement about every FTMO product or every firm. Read the current wording and related terms before drawing a conclusion about your account.
Rules can change, and a cached comparison article cannot approve a future trade. Use this page as a checklist for questions, not a substitute for the agreement governing the account. A vendor's statement that its software “works with prop firms” describes compatibility at best.
| Question | Detail to establish |
|---|---|
| Who owns the strategy? | Your decisions or a third-party source |
| Which accounts are linked? | Ownership, programme and allocation |
| Is copying permitted? | Own-account copying versus external signals |
| Is the execution method permitted? | Platform, EA, API and hosting restrictions |
| What risk rules apply? | Applicable loss calculations and trading restrictions |
Risk limits need their own review
The copier's quantity setting is not necessarily aware of the firm's account-wide loss calculation. Open losses, multiple routes and other trading activity may contribute to limits defined in the agreement. Review the actual calculation and its time boundary rather than substituting a familiar daily percentage.
The risk-management article explains why several modest entries can combine into material exposure. Target splitting and repeated full-size allocations deserve particular attention. A technically correct order can still produce an account outcome that breaches a programme rule.
Keep a record that matches the route
Save the relevant terms, the firm's clarification and the configuration used for the approved workflow. Recheck after adding an account, changing a source or switching programme stages. Approval for one arrangement should not be stretched to cover a materially different one.
Test on an appropriate demo environment before enabling the route, while recognising that successful demo execution proves no contractual permission. There is no universal “prop-safe” switch to select. The practical goal is a documented match between the firm's current rules and the precise workflow you operate.
Put the route to a demo test
Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.
Open TelegramSignal in AlgoWay