Ask for a rights and responsibilities schedule
| Area | Question to settle |
|---|---|
| Branding | Which client-facing elements can use the brokerage identity? |
| Accounts and groups | Which configuration and administration tasks are available? |
| Interfaces | Which integrations and permissions are supplied? |
| Operation | Who controls hosting, changes, monitoring and incidents? |
| Exit | Which records, exports and transition assistance are available? |
Request the answer in writing for the proposed arrangement. Current platform availability, permissions and any required approvals must be confirmed with the appropriate provider or rights holder.
Demonstrate the controls the team will actually use
List the daily work performed by sales operations, support, administrators and integration services. Then exercise the required workflows with the permissions offered to the brokerage. A demonstration using a provider administrator does not establish that the client will receive the same access.
Identify how a configuration change is requested when direct access is unavailable. Review the escalation route for an urgent issue, the evidence available to investigate it and the responsibilities that stay with the brokerage.
Make the decision traceable
Compare the required controls with the demonstrated rights and the work delegated to each organisation. Note conditions and exclusions rather than forcing every requirement into a simple yes/no column. A narrower arrangement may fit a focused brief, but only if the omitted controls are not needed for the operation.
Use the MT5 White Label scope to prepare requirements, and the provider evaluation guide to review evidence. Keep claims about ownership, licensing or independence tied to the actual agreement, not the marketing term.