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. Owners and administrators open all of it; the agent, people, security, compliance and billing admins and the auditor each see only the sections their role allows.

The overview screen

Organisation → 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 Organisation → 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.
Agent admin	No	Runs agents: registers them and issues their keys, writes agent governance, gates, policies and request rules, screens data and connects integrations. Reads the AI register, the audit log and analytics. Does not manage people, sign-in or billing.
People admin	No	Joiners and leavers: invitations, people, groups, sign-in, SSO and Directory Sync. Gives only the roles that run nothing (Workspace admin, Publisher, Viewer, Billing admin, Auditor), so cannot make anybody an administrator.
Security admin	No	Looks after sign-in and SSO, sharing, request rules, ethics, security settings, the audit log and legal holds, and reads people, agents and the AI register. Does not manage billing.
Compliance admin	No	Runs AI governance: the AI register, supplier assessments, AI policies, risk indicators, frameworks and incidents, and approves playbooks and prompts. Reads agents and their rules, analytics, the audit log, legal holds and evidence packs. Does not manage people, sign-in or billing.
Auditor	No	For internal audit, a risk function or an external assessor: reads the AI governance programme, agents and their rules, analytics, the audit log, legal holds and security settings, and downloads evidence packs. Changes nothing, and can be given a last day. On Business and Enterprise.
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

Owners and administrators change every section. The admin menu shows each other role only the sections it allows, and the sections check the role again on every visit and every change. A section a role reads but does not change says Read only at the top, with its controls switched off. Anyone else who opens an admin address is sent to their home screen.

Section	Admin	Agent admin	People admin	Security admin	Compliance admin	Auditor	Billing admin
Overview	Changes	—	—	—	—	—	—
Analytics	Changes	Reads	—	—	Reads	Reads	—
People	Changes	—	Changes	Reads	—	—	—
Groups	Changes	—	Changes	Reads	—	—	—
Agents	Changes	Changes	—	Reads	Reads	Reads	—
Platform overview	Changes	Changes	—	Reads	Reads	Reads	—
Identity & SSO	Changes	—	Changes	Changes	—	—	—
Sharing	Changes	—	—	Changes	—	Reads	—
Agent governance	Changes	Changes	—	Reads	Reads	Reads	—
Policy builder	Changes	Changes	—	Reads	Reads	Reads	—
Policy templates	Changes	Changes	—	Reads	Reads	Reads	—
AI overview	Changes	Reads	—	Reads	Changes	Reads	—
AI register	Changes	Reads	—	Reads	Changes	Reads	—
AI suppliers	Changes	Reads	—	Reads	Changes	Reads	—
AI policies	Changes	Reads	—	Reads	Changes	Reads	—
Risk indicators	Changes	Reads	—	Reads	Changes	Reads	—
Frameworks	Changes	Reads	—	Reads	Changes	Reads	—
ICT register	Changes	Reads	—	Reads	Changes	Reads	—
Data screening	Changes	Changes	—	Reads	Reads	Reads	—
Publishing & request rules	Changes	Changes	—	Changes	Reads	Reads	—
Ethics	Changes	Changes	—	Changes	Reads	Reads	—
Approval analytics	Changes	Reads	—	—	Reads	Reads	—
Held publishes	Changes	—	—	—	—	—	—
Security	Changes	—	—	Changes	—	Reads	—
Integrations & webhooks	Changes	Changes	—	Reads	—	—	—
Branding & domains	Changes	—	—	—	—	—	—
Evidence packs	Changes	—	—	—	Changes	Reads	—
Audit log	Changes	Reads	—	Changes	Changes	Reads	—
Legal holds	Changes	—	—	Changes	Changes	Reads	—
Billing	Changes	—	—	—	—	—	Changes
On Enterprise	Changes	Reads	—	Reads	Reads	Reads	—

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. Legal holds can be placed or released only by an owner, an admin, a security admin or a compliance admin. Only an owner gives the owner role, and only an owner or an admin gives an administrative role (admin, agent, people, security or compliance admin).

The admin guide

People and invitationsInviting people, roles, seats, suspending and removing.GroupsNamed sets of people to share with and to ask.AgentsAgent identities, their boundaries and their keys.Identity and single sign-onSAML and OpenID Connect, domains, and requiring SSO.Directory SyncProvisioning and deprovisioning from Entra or Okta, and group mappings.SharingGuests, secure links, public links and guest approvers.PoliciesWho must agree to what, and how many.EthicsRules that put a concern in front of the approver.Approval analytics and approvalsHow quickly the people in the loop answer what agents ask.AnalyticsWho reads your reports, and how often.Integrations and webhooksDeciding from Slack or Teams, and events sent to your own systems.Domains and brandingYour own domains, logo, colour and email sender.Security, audit and legal holdsReport content rules, the audit log and preservation.Billing and plansPlans, seats, invoices and changing plan.

Try it on your own agent.

Free to start, no card. Sign up with Google, Microsoft or GitHub, and the first page after hands you an API key.

Start free →

The overview screen#

Roles#

Who can open which section#

The admin guide#

Try it on your own agent.

The overview screen

Roles

Who can open which section

The admin guide