Admin overview and roles
What the admin area of Deliverd contains, which roles can open each part of it, and which roles take one of your plan's seats.
The admin area is where an organisation is run: who belongs to it and in what role, how people sign in, what may be shared and with whom, how agents are governed, and what the organisation pays for. Open it from Admin in the app, at /admin. Only the four administrator roles can open it, and each of them sees only the sections their role allows.
The overview screen
Admin → Overview shows the organisation at a glance: active members, seats in use, active reports, total report views, storage used and the current plan. Below that it lists the ten most recent security events — a blocked publish, a revoked share link or API key, a suspended member, or an agent refused by its own boundaries — with who caused each one. The full record is in the audit log.
Roles
Every member has exactly one organisation role, set when they are invited and changed on Admin → People. A seat is someone who can create and publish work. Approvals, reviews and requests for information are open to everyone in the organisation, viewers included, and need no seat.
| Role | Takes a seat | What it is for |
|---|---|---|
| Owner | Yes | Everything an admin can do, and the only role that can close the organisation. An organisation always keeps at least one active owner. |
| Admin | Yes | Runs the organisation: every admin section, including people, sign-in and billing. |
| Security admin | No | Looks after sharing, policies, ethics, security settings, the audit log and legal holds. Does not manage people or billing. |
| Billing admin | No | Manages the plan, payment method and invoices, and nothing else in admin. |
| Workspace admin | Yes | Creates and publishes work, and manages workspaces. No admin sections. |
| Publisher | Yes | Creates and publishes work. No admin sections. |
| Viewer | No | Reads what is shared with them, and answers approvals, reviews and requests for information. |
Who can open which section
The admin menu shows each person only the sections their role allows, and the sections themselves check the role again on every visit and every change. Anyone else who opens an admin address is sent to their home screen.
| Section | Owner | Admin | Security admin | Billing admin |
|---|---|---|---|---|
| Overview | Yes | Yes | — | — |
| Analytics | Yes | Yes | — | — |
| People | Yes | Yes | — | — |
| Invites | Yes | Yes | — | — |
| Groups | Yes | Yes | — | — |
| Agents | Yes | Yes | — | — |
| Identity & SSO | Yes | Yes | — | — |
| Sharing | Yes | Yes | Yes | — |
| Policies | Yes | Yes | Yes | — |
| Ethics | Yes | Yes | Yes | — |
| Decisions | Yes | Yes | — | — |
| Approvals | Yes | Yes | — | — |
| Domains | Yes | Yes | — | — |
| Webhooks | Yes | Yes | — | — |
| Security | Yes | Yes | Yes | — |
| Integrations | Yes | Yes | — | — |
| Branding | Yes | Yes | — | — |
| Audit log | Yes | Yes | Yes | — |
| Legal holds | Yes | Yes | Yes | — |
| Billing | Yes | Yes | — | Yes |
Two things sit on top of the table. On the Billing screen, only an owner sees the option to close the organisation, even though billing administrators can open the screen. And legal holds can be placed or released only by an owner, an admin or a security admin.