Run AI teams together with people you trust. Each Digio team has its own member list, roles, and access rules—so coordinators, operators, and reviewers share the same agents without sharing the wrong data.
In each team’s settings you add colleague emails and assign a role for that team—similar to sharing a Google Doc. Permissions apply only inside that team’s workspace: agents, tasks, boards, and billing visibility follow the role you choose.
Type one or more work emails, pick a role, and send. You can update or revoke access anytime from the same screen.
Five familiar roles. Owners and admins manage membership; editors run agents; members contribute within guardrails; guests can view or comment where you allow.
| Role | Typical permissions |
|---|---|
| Owner | Full control of the team, billing visibility, member management, and deletion. |
| Administrator | Manage members and team settings; run and configure agents. Cannot transfer ownership. |
| Editor | Create and edit agents, tasks, boards, and configs. Cannot change membership or billing. |
| Member | Work on assigned tasks and chats; limited changes to agent configuration. |
| Guest | Read-only or comment-only access to selected areas—useful for stakeholders and audits. |
Digio is built for mixed teams: operators assign work, specialists tune agents, and leads approve outputs. Collaboration keeps who did what visible—so automation scales without losing accountability.
An editor runs content agents and schedules posts; a member reviews drafts on the board; a guest from legal has view-only access to the publishing queue.
Developers use editor rights on a DevOps agent; team leads stay administrators and approve production-impacting task templates before agents run unattended.
A support agent drafts replies; members escalate tricky threads; an admin pins approved answers so the whole shift uses the same tone and policy.
A research agent compiles weekly briefs; analysts edit summaries; executives join as guests to read the latest run without touching agent settings.
Different members own day and night queues on the same agents; administrators rotate standing tasks and audit logs so coverage stays 24/7 without duplicate work.
Editors maintain shared agent configs and skill libraries; members run them on live tasks; owners control who can publish changes to production schedules.
Roles are scoped per team—not for your entire Digio account. Someone can be an editor on “Marketing AI” and a guest on “Finance automations” at the same time. Removing a person from one team does not affect their access elsewhere.
Audit-friendly — see who invited whom and which role changed, per team.
Least privilege — start guests or members on sensitive automations, promote to editor only when ready.
Token awareness — owners and admins see usage; editors cannot silently burn through plan limits without visibility.
Collaboration sits alongside the rest of the platform. Jump to the pages below to see how agents, skills, pricing, and referrals fit together.
Create a workspace, open team settings, and share access in minutes—registered colleagues get rights immediately; everyone else receives an email invite.
