Internal user features
SOPs for people who operate FFF-Frontend: the admin console (/admin) and the trader dashboard. Use these pages when you need “what do I click, who do I ping, and what happens to the customer.” Engineering architecture lives in other sections of this site.
How to read a page
Every feature page follows the same shape:
- When to use this screen — vs sibling screens.
- Who can open it / who to ping — permission in plain language, plus Risk / billing / KYC / payouts.
- Find the record — search, filters, export.
- Happy path — numbered steps and a flow diagram.
- Action catalog — each menu item: when to use it, customer impact, stop conditions.
- If this fails — vacation holds, already banned, payment already captured, KYC blocked, etc.
- Related screens — links.
:::info Who is this for Support, ops, compliance, and account managers. Superusers still follow the same SOPs; extra permissions only reveal buttons, they do not skip the “who to ping” rules. :::
Two products, one backend
| Surface | Who logs in | Sidebar |
|---|---|---|
| Admin console | Staff with RBAC | Five groups: Account Administration, Operations & Orders, Marketing & Affiliate, Accounts & Credits, Reporting & Logs |
| Trader dashboard | Customers (traders). Affiliated traders also see Affiliates | Obsidian rail: Dashboard, Messages, Accounts, Plans, Payouts, Certificates, Performance, Coach, News, Billing, Affiliates, Compliance, Settings, Help |
Staff who are superusers are sent to admin settings if they open /dashboard. Do not treat the trader dashboard as an admin tool.
Permissions in one paragraph
Admin menu items appear only if the operator’s role includes the matching grant (for example Trader manage for User Management). Superusers see almost everything except a few superuser-only screens (Realtime Insights). Individual ⋮ actions can require a second grant (ban, lock, tax invoice). If you can open a page but a button is missing, ask whoever owns Role Management — do not share a higher-privilege login.
Feature flags can hide Promotions, trader Certificates, News, and some affiliate tabs even when the operator has permission.
Related
- fff-risk-web — risk flags, payouts ops, and compliance cases that User Management can deep-link into.
- System architecture — how FFF-Backend, risk, and automation fit together.