Client operations around MetaTrader 4
The MT4 edition uses the TGS CRM foundation for client profiles, document review, trader portals, support requests and team tasks. Staff can retain the context of a client relationship while working within assigned roles. Analytics and local financial records support review of the operational workflow.
MT4 and MT5 are separate editions. Choose the platform for the accounts you actually operate, then confirm the scope of each workflow with the technical team.
- Client profiles, KYC documents and trader portal
- Staff roles, service requests, support and tasks
- Operational analytics and local financial records
REST integration and account visibility
The MT4 connector uses a REST gateway. Connection acceptance must confirm the exact gateway, the manager account and the requested account group. Authentication and server information alone do not establish that the manager can read every required account.
Before import, check that the account response is complete and that the account group matches the intended client population. Monitoring depends on verified API data; compatibility with every MT4 gateway is not assumed.
Current trading and financial scope
The current MT4 package retains the interfaces for MAM, Copy Trading and PAMM. Live Copy Trading and MAM execution are blocked. PAMM settlement, rollover and transfers are blocked pending verified market, account and execution support. Account creation is disabled and balance writes are disabled by default.
Cross-platform MT4-to-MT5 copying is not included. The MT5 trading workflows described elsewhere on this website apply to the MT5 edition. A module shown in the interface does not establish execution availability.
A separate installation and acceptance plan
Deploy MT4 with its own configuration, private database and encryption key. Begin with connection tests, verified account reads and access roles. Review the trader portal, KYC, requests and support before onboarding staff or clients.
Confirm any trading or financial requirement separately against the current connector. This phased acceptance process gives your team a clear record of the available operations and the integrations that still need work.
Implementation workflow
- 01
Define connections and account scope
- 02
Validate permissions and instrument settings
- 03
Test workflows in a demo environment
- 04
Agree production rollout and operations