Set up your organisation
A checklist for a new administrator: the order to set Deliverd up in, from inviting people to connecting the first agent, with the plan each step needs.
Everything below happens under Admin, which organisation owners and administrators see. None of it has to be finished before an agent can ask somebody something — only the first four steps matter on day one — but the order is the one that saves you redoing work.
The checklist
- 1
Invite people
Under Admin → People, Invite person and choose a role: viewers are free, and publishers, workspace administrators and administrators take a seat. Pending and past invitations are under Admin → Invites. See People and invitations.
- 2
Create groups
Groups are sets of people you can address in one go — share a report with Finance, or ask Legal for an approval, and any one of them can answer. Create them under Admin → Groups. See Groups.
- 3
Decide how people sign in
Out of the box people sign in with a password or an emailed link. To use your identity provider instead — Microsoft Entra ID, Okta, Google Workspace, another SAML 2.0 provider or an OpenID Connect provider — connect it under Admin → Identity & SSO. Single sign-on is on Team and above. When it is required, sign-in-free email links and chat buttons give way to it. See Identity and single sign-on.
- 4
Connect the first agent
Open Connect an AI tool and follow the steps for the tool you use. Most connect by signing in as you, with no token to copy; the agent then asks and publishes under your name. Ask it to request an approval from a colleague to see the whole round trip.
- 5
Give agents their own identities
An agent that runs on its own — on a schedule, in a pipeline — should have an identity of its own rather than borrow a person's: its own name on every request, its own keys, and limits on what it may publish. Create one under Admin → Agents. Agent identities are on Business and above. See Agents.
- 6
Write your policies
Under Admin → Policies, decide how many people must agree to which requests, who else is always asked, and who is brought in when a request waits too long. Publishing policies that hold a new version for approval, and rules for registered actions, apply on Business and above. See Policies.
- 7
Add ethics rules
Under Admin → Ethics, name the concerns you want a person to weigh before an agent acts. A rule can only add oversight; none can approve anything. Starter rules are there to adapt, and the optional model screen is on Business and above. See Ethics.
- 8
Set up notifications
Email and in-app notifications work from the start, and each person can turn on browser push on their own devices in Settings. To let approvers decide in chat, connect Slack or add the Microsoft Teams app under Admin → Integrations. To post events into a channel or your own systems, add a webhook under Admin → Webhooks. See Integrations and webhooks.
- 9
Choose your sharing settings
Under Admin → Sharing, decide whether guests are allowed, which email domains reports may be shared with, how long new links last, whether readers may download, and whether guests may decide approvals. Public links stay off until you turn them on. See Sharing.
- 10
Brand it and give it your address
Add your logo and colour, and an email sending domain, under Admin → Branding. Serve reports from your own subdomain or custom domain under Admin → Domains; custom domains are on Team and above. See Domains and branding.
- 11
Choose a plan
Compare plans and upgrade under Admin → Billing. Billing administrators can manage it without seeing anything else. See Billing and plans.
Tell people what to expect
Before the first agent asks anybody anything, point your colleagues at Your inbox and notifications and Deciding an approval. The one thing worth saying in advance: a request from an agent is answered by a person, on a page that works on a phone. Agents ask; they never decide.