Collaboration in Delphi is built into the core, not bolted on. Every dashboard carries its own permission set, so you can share a finance command center with your CFO without touching the operations view your site leads use. Invite the right people, pick what they can do, and get to work.
Open the Permissions tab
Head to the dashboard you want to share and open the Permissions tab from the left sidebar. You’ll see everyone who currently has access, their role, and any invitations that are still outstanding.
Only owners and admins can see this tab. If you don’t see it, you probably have editor access or lower — ask the dashboard owner to promote you or send the invitation on your behalf.
Send an invitation
Click Invite and enter your teammate’s work email address. You can invite anyone — they don’t need an existing Delphi account. If the email belongs to someone outside your organization, double-check before you send: access to this dashboard is exactly what you’re giving them.
We’ll email them a link to accept. The link is tied to the specific dashboard you invited them to, not a blanket platform invitation. Every send is recorded in your dashboard’s audit trail, so you always have a record of who invited whom and when. See Audit log for how to review that history.
Choose a role
Before you send, pick the role your teammate should have on this dashboard. Delphi has six roles: owner, admin, editor, analyst, auditor, and viewer. They range from full control down to read-only access to public data, with auditor sitting in the middle as a read-and-review role for compliance staff.
Default to the least privileged role that still lets your teammate do their job. You can always promote someone later, and it’s much easier to explain a promotion than to unwind a data exposure. For a full breakdown of what each role can see and do — including how data classification interacts with role — read Roles and access.
What happens after they accept
When your teammate clicks the link in the invitation email, they’ll be prompted to sign in (or create an account) and land directly on the dashboard you invited them to. Their role is applied the moment they accept, and the invitation itself is consumed — the same link can’t be reused.
From that point on, they’ll see the dashboard in their own dashboard list whenever they sign in. Their experience is automatically scoped to their role: an analyst sees the query tools and read access they’re entitled to, an editor can build visualizations and run scenarios, and a viewer gets a read-only experience with no exposure to restricted data.
If the command center you invited them to has nested initiatives below it, they pick up the same role on every initiative in the subtree — no per-child invitation needed. See Roles and access for the full cascade behaviour.
When a teammate has more than one address
People collect email addresses — an alias in the company directory, an older j.daniels@ format alongside a newer james@, a second domain from an acquisition. An invitation reaches your teammate as long as it’s sent to an address they’ve confirmed on their account, not only the one they sign in with.
Anyone can add addresses under Email Addresses in their account settings. Confirming one takes a link emailed to that mailbox, opened while signed in — proof they control the address, not just that they know it exists. Until an address is confirmed it counts for nothing: no invitation acceptance, no search match.
If your organization runs on Google Workspace, there’s usually nothing to do — alias addresses from your directory are picked up automatically and arrive already confirmed.
Shared addresses are the deliberate exception. A mailing list or team inbox — leadership@, support@, anything a group of people can read — can’t be claimed as a personal address, because an invitation accepted from it could have been accepted by anyone on the list. If Delphi refuses an address for this reason, invite the actual person instead.
The invite search on the Permissions tab understands all of this. Start typing a name or email and Delphi suggests matching colleagues; paste a full address someone has confirmed and it finds them too, shown once, whichever of their addresses you used.
Share with your whole organization
Inviting people one at a time is right for a dashboard with a defined audience. For one everybody should see, turn on organization-wide sharing instead: anyone signing in with a verified work email gets access without an invitation.
Pick the role they get when you turn it on. Viewer keeps the dashboard read-only for the wider organization; editor makes it a shared workspace. The setting caps at editor — admin and owner are always granted to named people, never to an organization — and raising it above viewer takes a tenant administrator.
The two combine, taking whichever role is higher. Share a dashboard organization-wide as viewer, invite three analysts as editors, and they keep editor while everyone else reads. Share it as editor and the people you named get editor too.
External collaborators are not included — someone invited on a personal or partner address keeps exactly the access you gave them. Full details in Roles and permissions.
If an invitation doesn’t arrive
Almost always it’s sitting in a spam or quarantine folder. Ask your teammate to check theirs, and ask your IT team whether messages from mail.outcome.com are being held before delivery.
If the email arrived but accepting doesn’t work, check which account they’re signed in with. An invitation sent to an address your teammate hasn’t confirmed on their account can’t be accepted from it — once they add and confirm that address under Email Addresses in account settings, the original invitation works as sent, no resend needed.
If it genuinely never arrived, resend it from the Permissions tab — the new link supersedes the old one.
Manage existing access
Back on the Permissions tab, you can change anyone’s role at any time by selecting a new role from the dropdown next to their name. Changes take effect on their next request — there’s no need to sign them out.
To remove someone, use the remove action in the same row. Their access is revoked immediately, and the change is audit-logged like every other permission action. If someone leaves your organization, removing them here is enough to cut off dashboard access; you don’t need to coordinate with IT or wait for an identity provider sync.
Outstanding invitations appear in a separate list. If a teammate hasn’t accepted yet, you can revoke the invitation the same way — the link in their email stops working the moment you do.