Unknown block type:
SchoolHeaderUnknown block type:
SchoolNavForex CRM Admin
Every client, every role and every action in one console
Why the admin console
Run the desk
from one screen
Everything a brokerage does in a day passes through here — and nothing has to be looked up twice.
-
One client record
Accounts, documents, deposits, tickets and the partner who introduced them all hang off a single record. Open a client once and the whole relationship is on the screen, not spread across four systems that each know a different part of it.
-
Roles and permissions
Who sees what is set per role, down to the field. A sales desk sees its own book, finance sees the ledger, and nobody sees more than the job needs — which is the answer to most of what an audit asks about access.
-
The KYC queue
Documents arrive, Veriff and Sumsub run their checks, and only the cases that need judgement reach a person. Approvals and rejections are logged against the operator who made them, with the file attached.
-
Money movement
Deposits, withdrawals, transfers and manual adjustments in one place, released on approval rules rather than out of an inbox, each carrying the provider’s own reference so reconciliation has something to match on.
-
Audit trail on everything
Every action in the portal is written down with the client, the operator and the time. Not a log you have to go and find, but the record a compliance review actually asks for, ready before it is asked for.
-
Reporting without exports
Desk, partner and client numbers are built from the same data the console runs on, so a report never disagrees with the screen it came from and nobody spends a morning reconciling two spreadsheets.
Who works in it
One console, every desk
Access is set per role, so the same screen shows a different day’s work depending on who signs in.
-
Sales
Their own book, the leads assigned to them and the call that is due next — and nothing at all from another desk’s pipeline.
-
Onboarding
The KYC queue and little else: documents in, checks run, and the handful of cases that genuinely need a person to look at them.
-
Finance
Deposits, withdrawals and the ledger, with approval limits set per operator rather than per department, so a stand-in never inherits more than they should.
-
Partnerships
The IB tree, the rebate rules behind it and what each partner is owed this month, without a spreadsheet standing between the two.
-
Support
Tickets sit against the client record, so the account, the last deposit and the open case are already on screen when the call is answered.
-
Compliance
Read across everything, change nothing, and pull the trail out without having to ask another team to run an export first.
The admin portal
Run the whole desk from one screen
Clients, partners, compliance and money movement stop living in five systems and start living in one your team already knows.
- Live client records
- The IB tree at a glance
- KYC queue and audit trail
- Payouts without re-keying
Questions about the console
Before you give anyone a login
The things a desk usually wants settled before it moves its clients into a new admin portal.
-
To the field. A role decides which modules open, which records inside them are visible, which fields on those records can be read and which can be changed, and what the operator is allowed to approve. A sales desk can see its own book and nothing from another desk’s pipeline; compliance can read across everything and change none of it. Approval limits sit on the operator rather than the department, so covering for someone on leave never quietly hands them a larger limit than they should have.
-
Every one. Each action in the portal is written against the client it touched, the operator who did it and the time it happened — approvals, rejections, refunds, manual adjustments, field edits and the logins themselves. The trail cannot be edited from inside the console, and it is exported from the same screen rather than pulled by another team, which is usually the difference between answering a compliance review the same day and spending a week assembling one.
-
Yes, and so does everything around it. White label is how the product ships rather than an upgrade on top of it: the admin console, the IB portal and the trader terminal all carry your name, your colours and your domain, and our mark appears nowhere a client or a partner can see it. The console is the screen your own team looks at all day, so it is worth it reading as your system rather than someone else’s.
-
Either way, and it is the same platform. Brokers whose compliance team needs client data to stay on infrastructure they control deploy it on their own server; desks that would rather not run servers let us host it. Deployment, upgrades and monitoring are handled in both cases — the choice is about where the data sits, not about which version of the product you get.
-
They come across with their history. Client records, trading accounts, documents already verified, the partner tree and the balances all migrate together, so a client who logs in after the move finds the account they had rather than a blank one. The platform connections are set up alongside it, which means a desk switching from another system is not also switching how it trades while it learns a new console.