Skip to main content
Organizations use their own set of roles, separate from team roles. Every person in an organization has exactly one organization role, and that role controls what they can do at the organization level — managing teams, approving join requests, editing domain settings, and viewing cross-team insights. A person’s organization role is independent of their role inside any specific team. The same user can be an organization Admin and still be a regular team Member in one of the teams inside that organization.

​
Understanding the Roles

Each organization role is designed for a distinct type of user. The key question is: how much oversight does this person need across the company?
  • Member — For colleagues who primarily work inside one or a few teams. Members can see the organization’s structure and the list of teams in it, and they can join any auto-join team or request to join teams that require approval.
  • Admin — For champions who help run the company’s Duvo footprint. Admins can create new teams inside the organization, manage domain settings, approve organization and team join requests, invite new members to the organization, and view cross-team insights such as the Clarity view. Admins automatically have access to every team in the organization and can open any team without joining it.
  • Owner — For the people ultimately responsible for the organization. Owners have all Admin capabilities plus the ability to manage Admins and update core organization settings. Owners automatically have access to every team in the organization.
  • Executive — The most senior role in an organization, reserved for top-level stakeholders. Executives have full control of the organization, including managing other Owners and Executives. Every organization must have at least one Executive. Executives automatically have access to every team in the organization.

​
Permissions by Role

​
Organization Management

​
Teams Inside the Organization

​
Joining every team at once

Executives and Owners can join all teams in one step instead of opening each team card. The Join all teams action appears on the organization welcome screen and on Browse teams, and asks for confirmation before it runs.
  • It joins every team in the organization, including teams that require approval, so it is hidden while a search or filter is narrowing the list.
  • It creates a real membership in each team, visible to those teams. An Executive joins as team Administrator, an Owner as team Owner.
  • Teams you already belong to keep their existing role, so the action is safe to run again after new teams are created. You can leave any team later.

​
Cross-Team Insights

  • Open and understand the landscape — All organization members can open Process Landscape. Folders and capabilities form the visible organization skeleton. Inaccessible processes appear as Restricted process; only granted processes render in full.
  • Propose areas and processes — All organization members can add an area or a process as a proposal: a suggestion for review, marked as proposed and shown alongside confirmed work. A proposal never activates an area, never creates a real process, and never changes or removes anything that already exists — so proposing is safe for everyone, while confirming a proposal stays with the roles below.
  • 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.

​
How Organization Roles Interact With Team Roles

Organization roles and team roles are applied independently, but they combine in a few important ways:
  • Admins, Owners, and Executives have read-only virtual access to every team in the organization. They can open any team and see its contents without joining it. To act inside a team — run agents, change settings, or make any other edit — they join it and receive the team role mapped from their organization role (see how admins get access to teams).
  • Members interact with teams the same way any individual contributor would. Their organization role only controls discovery and visibility at the organization level.
This separation means a person can be an Executive at the organization level (for strategic oversight) while still choosing to be a regular team Member inside the teams they actively work in — or not join those teams at all.

​
Choosing the Right Role

Pick the role based on what the person needs to do at the organization level: Every organization must keep at least one Executive at all times.

Organizations Overview

What organizations are and how they work

Teams Overview

How teams work inside (and outside) an organization

Team Roles and Permissions

Team-level roles, which apply separately from organization roles