The operator console
Operator roles, network access, hardware keys and the operator dashboard.
The operator console is where the Sauti platform team runs the service. It is separate from the campaign workspace, on its own restricted address, and every action in it is audited in the operator audit chain.
Operator roles#
| Role | Scope | Main responsibilities |
|---|---|---|
| Super admin | Whole platform | Everything: organisations, plans, providers, payments, platform controls, keys and reveals |
| Data officer | Assigned organisations | List imports, intake review, deduplication queues |
| Operator DPO | Whole platform | Data subject requests, data protection registers |
| Operator support | Assigned organisations, through grants | Read-only troubleshooting of tenant configuration |
| Finance | Whole platform | Wallets, pricing, invoices, revenue, provider balances |
Manage operator roles in Settings › Operator roles and operator accounts in Users. A super admin can create operator accounts (the password is shown once) or send 72-hour invitations.
Access rules#
- The console is reachable only from the operator network or allowlisted addresses.
- Sessions end after 30 minutes of inactivity.
- Super admins, data officers and DPOs complete a passkey or hardware-key step after their authenticator code.
- Sensitive actions (reveals, exports, credential changes) ask for a reason and a fresh authenticator code, and some need a second operator.
The operator dashboard#
The dashboard shows a seven-day delivery trend (privacy-banded), queue depth, wallet exposure, provider circuit observations and shortcuts to the main controls.
Navigation#
| Group | Pages |
|---|---|
| Organizations | Organisation records, plans and pricing, organisation administration, support workspace |
| Operations | Audit, cross-tenant view, kill switches, manage records, platform controls, system health, tenant notices, wallets |
| Providers | Provider accounts, SMS senders, SMS routing, go-live check, email domains, Telegram bots, voice accounts, WhatsApp policy, social platform apps |
| Payments | Merchant accounts, card and bank checkout, donation channels, payment exceptions, revenue and invoices, unpaid invoice holds |
| Compliance | Compliance queue, content screen, data protection registers, gender and age audiences |
| Imports | Data imports, supporter capture and resolving, supporters, import API tokens |
| Geography | Reference geography, phone networks, polling coordinates |
| Exports | Contact privacy (reveals and approved exports) |
| DSR cases | Data subject requests |