Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt

Use this file to discover all available pages before exploring further.

Duvo uses team-level roles to control what each member can see and do within a team. Every team member is assigned exactly one role, and roles are scoped per team — a user can have different roles in different teams.

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 assignments or connections.
  • Member — For people who use assignments but do not build them. Members can run assignments shared with them, connect their own connections, and manage files — everything they need to get work done with assignments others have created.
  • Builder — For people who create their own assignments. Builders can build, test, and iterate on their assignments, but they cannot edit assignments created by others. When a Builder creates an assignment, they own it and have full control over its SOP, connections, and revisions.
  • Manager — For people who oversee assignments across the team. Managers can create, edit, and delete any assignment — not just their own. They also manage case 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 job 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

CapabilityOwnerAdministratorManagerBuilderMemberClarity Member
Manage billingYesYes------------
View and edit team settingsYesYes------------
Delete teamYesYes------------
Add or remove team membersYesYes------------
Update member rolesYesYesYes---------
Invite new membersYesYesYes---------
View team membersYesYesYesYesYesYes

Assignments

“Own only” means the permission applies only to assignments the user created.
CapabilityOwnerAdministratorManagerBuilderMemberClarity Member
Create new assignmentsYesYesYesYes------
Edit any assignmentYesYesYes---------
Edit own assignmentsYesYesYesYes------
Delete any assignmentYesYesYes---------
Delete own assignmentsYesYesYesYes------
Create revisions on any assignmentYesYesYesOwn only------
Create revisions on own assignmentsYesYesYesYes------
View and run assignmentsYesYesYesYesOwn only---
Manage assignment foldersYesYesYesYes------

Connections and Resources

CapabilityOwnerAdministratorManagerBuilderMemberClarity Member
Access connectionsYesYesYesYesYes---
Add and manage custom connectionsYesYesYes---------
Manage files and skillsYesYesYesYesYes---
Manage API keysYesYesYes---------
Access browser loginsYesYesYesYes------

Analytics and Intelligence

CapabilityOwnerAdministratorManagerBuilderMemberClarity Member
View team insightsYesYes------------
View all team members’ jobsYesYes------------
Access ClarityYesYesYesYesYesYes
Contribute to ClarityYesYesYesYesYesYes
Manage Clarity processesYesYesYes---------
Manage case queuesYesYesYes---------

Builder Ownership Model

The Builder role uses an ownership model for assignment editing. When a Builder creates an assignment, they become its owner and have full editing capabilities on that assignment — including modifying the SOP, adding connections, creating new revisions, and deleting the assignment. For assignments created by other team members, Builders have view and run access only. To edit assignments they did not create, a user needs the Manager role or above.