Updated 23 Oct 2026 · written by the team that builds these panels
Master panel vs admin panel: where the line sits
A master panel creates and funds agents. An admin panel creates masters, sets the top-level share and settles the book. The line exists so that no master can see another master's agents — and no admin has to micromanage them.
The boundary in practice
| Action | Master | Admin |
|---|---|---|
| Create an agent | Yes | Yes |
| Set agent share % | Within its cap | Any |
| Approve a deposit | For its own agents | Any |
| Change a settlement rate | No | Yes |
| See another master's book | No | Yes |
Why the cap matters
The master's share cap is the whole point of the hierarchy. Without it, a master can undercut the platform's own rate and take the book with them when they leave. Set the cap before you recruit, not after the first argument.
What to check before you hand a master a login
- The cap is enforced server-side, not just hidden in the UI.
- Their agents cannot be moved to another master without an admin action.
- Every master action lands in the same audit log as admin actions.
- Their settlement schedule is visible on their own screen, so disputes start with data.
Questions people actually ask
Can a master create another master?
Only if you allow it. Most platforms keep master creation at admin level.
What happens to agents if a master leaves?
A proper build lets an admin reassign agents without losing their history.
Is the master's view read-only for payouts?
No — masters approve for their own agents; the admin settles.
Next step: send your tier and the number of agents on WhatsApp — you get a written rate card and a staging date the same day. Message us →