Operator panel
The operator panel lives under /operator and is the operator’s view. It
is deliberately its own world: its own accounts, its own cookie, its own
roles. A tenant login never gets in here, and an operator login opens no
tenant application.
It is reachable only via the direct link — the normal interface has no reference to it.
Accounts and roles
Section titled “Accounts and roles”| Role | May |
|---|---|
| admin | everything, including management of operator accounts |
| consult | registry and reporting |
| support | assist tenant users (contact details, password reset) |
The first account is created on the very first start from
DNSE_OPERATOR_USER and DNSE_OPERATOR_PASSWORD and is an administrator.
Further accounts are created by an administrator in the panel.
Every operator account can secure itself with TOTP two-factor under My account; disabling it requires the current password. Given the reach of these accounts, this is strongly recommended.
What the panel shows
Section titled “What the panel shows”Dashboard — metrics on organisations, users, zones and accounts, plus the distribution across plans.
Organisations — the registry: per tenant its plan, metrics and user list. From here you can change plans, correct contact details and reset passwords. With backups configured, restore points and Export now are added (Backup and restore).
System — the cluster configuration as a read-only view: which core settings are set via environment variables and how organisations and users are distributed across the regions.
Settings and messages — the platform level: core settings (SMTP, DynDNS hostnames, public address) and portal messages that appear as banners for all tenants. The operator maintains both once, centrally; these pages are hidden in the tenants’ admin panels.
No DNS data
Section titled “No DNS data”The registry shows numbers, not zones. An operator sees that an organisation manages 42 zones — not which ones. Whoever is meant to help with content needs a regular share in the affected project.
Machine access
Section titled “Machine access”DNSE_OPERATOR_TOKEN allows access to the operator API without sign-in
(header X-Operator-Token) and counts as an administrator. It is intended
for the checkout frontend and automation — not as a convenient entrance for
humans. Where it is not needed, it should be omitted.