Understanding the Roles
Each role is designed for a distinct type of team member. The key question is: what does this person need to do in Duvo?- Clarity Member — For people contributing to process mapping. They access Clarity to document and refine processes but do not interact with agents or connections.
- Member — For people who use agents but do not build them. Members can run agents shared with them, connect their own connections, and manage files — everything they need to get work done with agents others have created.
- Builder — For people who create their own agents. Builders can build, test, and iterate on their agents, but they cannot edit agents created by others. When a Builder creates an agent, they own it and have full control over its AOP, connections, and revisions.
- Manager — For people who oversee agents across the team. Managers can create, edit, and delete any agent — not just their own. They also manage queues and have full access to connections and resources.
- Administrator — For people who run the workspace. Administrators have all the capabilities of a Manager, plus they can manage team members, roles, settings, API keys, and view every team member’s schedules and run results in one place.
- Owner — For the person ultimately responsible for the team. Owners have full Administrator access plus control over billing, team deletion, and the ability to assign the Owner role to others. Every team must have at least one Owner.
Permissions by Role
Team Management
| Capability | Owner | Administrator | Manager | Builder | Member | Clarity Member |
|---|---|---|---|---|---|---|
| Manage billing | Yes | Yes | --- | --- | --- | --- |
| View and edit team settings | Yes | Yes | --- | --- | --- | --- |
| Delete team | Yes | Yes | --- | --- | --- | --- |
| Add or remove team members | Yes | Yes | --- | --- | --- | --- |
| Update member roles | Yes | Yes | Yes | --- | --- | --- |
| Invite new members | Yes | Yes | Yes | --- | --- | --- |
| View team members | Yes | Yes | Yes | Yes | Yes | Yes |
Agents
“Own only” means the permission applies only to agents the user created.| Capability | Owner | Administrator | Manager | Builder | Member | Clarity Member |
|---|---|---|---|---|---|---|
| Create new agents | Yes | Yes | Yes | Yes | --- | --- |
| Edit any agent | Yes | Yes | Yes | --- | --- | --- |
| Edit own agents | Yes | Yes | Yes | Yes | --- | --- |
| Delete any agent | Yes | Yes | Yes | --- | --- | --- |
| Delete own agents | Yes | Yes | Yes | Yes | --- | --- |
| Create revisions on any agent | Yes | Yes | Yes | Own only | --- | --- |
| Create revisions on own agents | Yes | Yes | Yes | Yes | --- | --- |
| View and run agents | Yes | Yes | Yes | Yes | Own only | --- |
| Manage agent folders | Yes | Yes | Yes | Yes | --- | --- |
Connections and Resources
| Capability | Owner | Administrator | Manager | Builder | Member | Clarity Member |
|---|---|---|---|---|---|---|
| Access connections | Yes | Yes | Yes | Yes | Yes | --- |
| Add and manage custom connections | Yes | Yes | Yes | --- | --- | --- |
| Manage files and skills | Yes | Yes | Yes | Yes | Yes | --- |
| Manage API keys | Yes | Yes | Yes | --- | --- | --- |
| Access browser logins | Yes | Yes | Yes | Yes | --- | --- |
Analytics and Intelligence
| Capability | Owner | Administrator | Manager | Builder | Member | Clarity Member |
|---|---|---|---|---|---|---|
| View team insights | Yes | Yes | --- | --- | --- | --- |
| View all team members’ runs | Yes | Yes | --- | --- | --- | --- |
| Access Clarity | Yes | Yes | Yes | Yes | Yes | Yes |
| Contribute to Clarity | Yes | Yes | Yes | Yes | Yes | Yes |
| Manage Clarity processes | Yes | Yes | Yes | --- | --- | --- |
| Manage queues | Yes | Yes | Yes | --- | --- | --- |
Builder Ownership Model
The Builder role uses an ownership model for agent editing. When a Builder creates an agent, they become its owner and have full editing capabilities on that agent — including modifying the AOP, adding connections, creating new revisions, and deleting the agent. For agents created by other team members, Builders have view and run access only. To edit agents they did not create, a user needs the Manager role or above.Related Topics
- Teams Overview — How teams work and how to structure them
- Guardrails for High-Risk Automations — How roles apply when reviewing AOP changes on high-risk agents