# Organizations Overview ### 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. Without an organization, each team is a standalone workspace with its own members and settings. With an organization, teams become part of a wider container that shares 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, assignments, 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](/organizations/roles-and-permissions.md). *** ### 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; personal email addresses (for example, public webmail providers) continue to be prompted to create a standalone team, not to join an organization. #### Organization discovery modes Each organization has a discovery mode that controls what happens when someone signs up with a matching domain: | Mode | What happens | | ------------------- | ---------------------------------------------------------------------------------------------- | | **Auto-join** | The person is added to the organization immediately as a Member. | | **Request to join** | 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, or generate a shareable invite link. Invitees accept the invitation and land in the organization with the role the inviter chose. *** ### Team Discovery Inside an Organization 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. Anyone can still create a **standalone team** outside of any organization. Standalone teams work exactly as they always have — they just don't benefit from organization-level discovery, domain settings, or cross-team views. *** ### Cross-Team Views Organizations unlock company-wide views that aren't available to a single team on its own. The first cross-team view is for **Clarity**: it lists every Clarity process across every team in the organization in one place, so champions can see the full picture of how work is being mapped across the company. More cross-team views are planned to help champions get insight across teams without having to switch between team workspaces. *** ### Organizations vs. Standalone Teams | Capability | Standalone Team | Team in an Organization | | ------------------------------------------ | --------------- | ----------------------- | | Team members, assignments, and connections | Yes | Yes | | Discovery mode for organization members | --- | Yes | | Company-wide domain auto-join | --- | Yes | | Cross-team Clarity view | --- | Yes | | Organization-level admin roles | --- | Yes | | Anyone in the team can create more teams | Yes | --- (admin-level only) | *** ### Related Topics * [Roles and Permissions](/organizations/roles-and-permissions.md) — Every organization-level permission, broken down by role * [Teams Overview](/teams/teams-overview.md) — How individual teams work inside an organization * [Team Roles and Permissions](/teams/roles-and-permissions.md) — Team-level roles, which apply independently of organization roles --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.duvo.ai/organizations/organizations-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.