Skip to main content
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 process knowledge. They can add interview evidence and manage their own captures, but they cannot edit generated process content or use agents and 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 agents and help maintain Clarity. Builders can build, test, and iterate on their own agents, create Clarity processes, and edit any Clarity process they can access in their team. They can delete only the Clarity processes they created.
  • 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, 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

Agents

“Own only” means the permission applies only to agents the user created.

Connections and Resources

Analytics and Intelligence

Clarity content editing is team-wide for Builders without bypassing restricted-process access. A Builder can rename an accessible process, update its guidance, and edit generated process content even when another teammate created it. Lead Builders and above can mark a process complete or reopen it for review. The creator or a Manager must still handle generation, sharing, visibility, and access. Builders can delete only processes they created; Managers can delete any team process. Clarity Members contribute browser interviews (voice or screen share) only; file uploads and meeting notetaker require Member or above. The Manage Clarity settings and structure permission lets team Owners, Administrators, and Managers maintain process nodes for their team.
  • Open and understand the landscape — All organization members can open Process Landscape. On the List and Map views, organization Admins, Owners, and Executives see the complete area hierarchy, including empty areas when no search or filter (such as the Team filter) is active; everyone else sees the processes they can open and the areas that hold them (plus an empty area they just created or emptied by moving a process in the current session, until filters change or the page reloads), and inaccessible processes do not appear. Builders and above on a landscape team still see every active area, including empty ones, in the Area picker when adding or moving a process.
  • Add areas and file processes — Managers and above on a team in the organization can add areas and sub-areas. Builders and above can file or move their team’s processes into any area.
  • Maintain process nodes — Managers can maintain process nodes for teams they manage. Organization Executives, Owners, and Admins can maintain the skeleton and all process nodes.
  • Generate the landscape — Only organization Executives and Owners can generate Process Landscape.
  • Assign ownership — Process ownership assignment remains limited to organization Admins, Owners, and Executives.

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 Lead Builder role or above. Any team member who can run an agent can still set up their own triggers on it, using their own connected account, even when they cannot edit the agent. Someone who can edit the agent adds the integration to it first, such as Gmail or Slack; members then connect their own account and set their trigger filters. Connecting a team connection, or an integration the agent does not use yet, needs edit rights. Schedules, case triggers and everything else on the agent need edit rights. On a team on automation revisions, some trigger settings are shared with teammates, as described below. Inside an automation, each agent keeps its own rule. Changing one agent there needs edit rights on that agent: its build in a draft, its schedules, or removing it. On a team on automation revisions whose triggers belong to the automation, a trigger that is part of the automation shares its filter with everyone subscribed to it. Changing that filter or its trigger type, or adding a trigger with a filter no teammate uses yet, needs edit rights on that agent. Members can still pause, reconnect and remove their own triggers there, and add a trigger with the same settings a teammate already uses. A trigger a member set up before the agent joined the automation stays theirs to change. Otherwise members set up their own triggers as described above. Making a draft active, or discarding it, counts as changing the agents the draft changes. A Builder can do these for the agents they created, even when the automation also holds a teammate’s agents. Changes to the automation as a whole affect every agent in it: renaming or deleting it, its queues, tabs and overview. A Builder can make these only when they created every agent in the automation. Adding an agent to an automation needs both. Users with the Lead Builder role or above can change any automation. Clarity intentionally works differently: Builders can edit process content across their team so process documentation stays collaborative. Ownership still controls deletion and administrative actions.

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