> ## 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. # Organizations Overview > How organizations group multiple teams under one company-wide container with shared discovery, domain settings, and cross-team views. ## Introduction Organizations are a layer above teams in Duvo, designed for companies that run Duvo across more than one team. An organization gives champions — the people driving Duvo adoption across a business — a single place to oversee every team in their company: who belongs to them, how colleagues join them, and what work is happening across them. Every newly created team belongs to an organization. A single-team organization behaves much like a team on its own — its own members and settings, nothing shared — while an organization with several teams gives them shared discovery rules, domain settings, and cross-team views. ## What is an Organization? An organization is a company-wide container that groups multiple teams together. It determines: * **Which teams belong to your company** in Duvo * **How colleagues from your company find and join** those teams * **Which email domains count as "your company"** for automatic onboarding * **Who can see activity across every team** from one place Think of an organization as the company, and teams as the departments, functions, or projects inside it. Teams keep their own members, agents, connections, and roles — the organization sits above them. ## Why Organizations Matter **A single pane of glass for champions.** Admins who oversee multiple teams can monitor, join, and manage them without switching workspaces. **Frictionless onboarding for colleagues.** Domain auto-join and team discovery modes let new colleagues land in the right place as soon as they sign up, instead of waiting for a manual invite. **Company-wide visibility.** Cross-team views show what's happening across every team in the organization, starting with a consolidated view of every Clarity process. **Consistent structure at scale.** As more teams form inside a company, organizations keep them connected instead of drifting apart into isolated workspaces. ## Organization Roles at a Glance Organization roles are separate from team roles. Every member of an organization has exactly one organization role, which controls what they can do at the organization level. That same person can still have a different role inside each team they belong to. There are four organization roles: * **Member** — Can see the organization's structure and request to join teams. * **Admin** — Can manage teams, approve join requests, configure domain settings, and see insights across the company. * **Owner** — Has all Admin capabilities plus broader control over the organization. * **Executive** — The highest organization role, with full control over the organization, including managing Owners and other Executives. For a detailed breakdown of every permission, see [Roles and Permissions](/user-guide/organizations/roles-and-permissions). ## Getting Your Organization Set Up Before any of this applies, the organization has to exist and someone has to hold the most senior role in it. That provisioning step — how the organization is created, who becomes the first admin, and what they should set up before inviting colleagues — is covered in [Organization Setup](/user-guide/organizations/organization-setup). ## Joining an Organization Duvo supports three ways for someone to become part of an organization. ### Domain auto-join Organization admins can add one or more **work email domains** to the organization. When someone signs up with an email address on a whitelisted domain, Duvo recognizes their company and places them into the organization automatically — or routes them through a join request, depending on the organization's discovery mode. Domain settings are managed by admin-level roles. Only work-email domains are accepted; someone signing up with a personal email address (for example, a public webmail provider) gets an organization of their own rather than joining an existing one. ### Organization discovery modes Each organization has a discovery mode that controls what happens when someone signs up with a matching domain: | Mode | What happens | | - | - | | **Open access** | The person is added to the organization immediately as a Member. | | **Request access** | The person submits a join request, which an admin-level role reviews and approves or declines. | ### Invitations and invite links Admin-level roles can also invite specific people to the organization by email, choosing the organization role they receive. A shareable invite link is different: it always grants the Member role. Email invitations are valid for 30 days. If an invitation expires before the person accepts it, an admin-level role must send them a new invitation. Shareable invite links don't use this 30-day limit. ## Team Discovery Inside an Organization ### Welcome page for new joiners The first time someone joins an organization and opens it without belonging to any of its teams, they land on a welcome page that introduces the organization and lists its teams. From there they can search for a team by name and join it right away (for auto-join teams) or request to join (for teams that require approval). They can also skip this step and browse teams later — the welcome page only appears once. Once someone is in an organization, they can see the list of teams in it and choose which ones to join. Each team has its own discovery mode, set by team admins: | Team mode | What Members see | | - | - | | **Auto-join** | Any organization member can join the team directly, without approval. | | **Requires approval** | Organization members can request to join, and a team admin approves or declines the request. | This means a sensitive team (for example, Finance) can require approval, while a more open team (for example, a company-wide "General" team) can be set to auto-join. Team discovery modes apply only to organization members — people outside the organization still need a team invite as before. Organization Admins, Owners, and Executives automatically have access to every team in the organization, so they do not need to request to join. ## Creating Teams in an Organization Inside an organization, team creation is restricted to **higher-privileged organization roles** (Admin, Owner, and Executive). Regular Members cannot spin up new teams inside the organization; this keeps the team list curated and prevents sprawl as a company scales. Every newly created team belongs to an organization — there is no way to make one that sits outside all of them. If you sign up without a matching organization, for example with a personal email address, Duvo creates one for you together with your first team and makes you its Executive. You can then claim a domain, invite colleagues, and rename it in [Organization Setup](/user-guide/organizations/organization-setup), or ask Duvo support to move your team into an organization that already exists. A **standalone team** created before every team belonged to an organization keeps working as it always has. Ask your Duvo contact to move it into an organization — see [Organization Setup](/user-guide/organizations/organization-setup). ## Cross-Team Views Organizations provide a company-wide **Process Landscape** that shows how work is organized across teams. * **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. * **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. * **Read and adjust the priority heatmap**: **High** priority is visually emphasized on the map. **High**, **Medium**, and **Low** priorities appear in the tree and process details, with the reason in the process details. Managers can override or clear priorities for processes owned by teams they manage; organization Admins, Owners, and Executives can do this across the organization. Select **Not set** to clear a priority and return the process to the unassessed state. * **Navigate the map**: The map view zooms and pans like a design canvas. Pinch, or hold **Ctrl**/**⌘** and scroll, to zoom at the cursor; scroll to move around; drag empty canvas, or hold **Space** and drag from anywhere, to pan. The controls in the top-right corner zoom in and out, open zoom presets from the percentage, and fit the whole landscape to the window. Click a value-chain heading to zoom to that row, and double-click empty canvas to zoom in. Keyboard shortcuts: **Ctrl/⌘ +** and **Ctrl/⌘ −** zoom, **Ctrl/⌘ 0** returns to 100%, and **Shift+1** fits the landscape. The map remembers your zoom level for your next visit. While you are zoomed into part of the landscape, a small overview map appears in the bottom-left corner; click or drag it to move around. More cross-team views are planned to help teams get insight across the organization without switching between team workspaces. ## Related Topics How the organization gets created and the first admins get access Every organization-level permission, broken down by role How individual teams work inside an organization Team-level roles, which apply independently of organization roles This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.