> ## 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. # Organization Setup > How an organization gets created, who becomes the first admin, and the setup steps that bring the rest of the company onto Duvo. Before roles and discovery settings matter, the organization has to exist and someone has to hold the most senior role in it. This page covers how that happens and what the first admin should set up. For what an organization *is*, see [Organizations Overview](/user-guide/organizations/organizations-overview). ## How an organization gets created When nobody from your company has used Duvo before, the first person to sign up with a work email gets everything created for them. Duvo makes an organization named after their email domain — signing up as `you@acme.ai` gives you an organization called **Acme** — claims that domain, adds a first team called **My Team**, and gives that person the **Executive** organization role, the most senior one. They land straight in organization setup to confirm the name, domain, and how colleagues can join. The generated names stick until someone changes them, so renaming the organization and the team is usually the first thing to do. The first person to sign up from your company becomes the Executive. On a larger rollout, it helps to decide who that should be before you share Duvo internally — but nothing is locked in. An Executive can appoint more Executives and Owners at any time. To transfer responsibility, promote the new Executive first. If the previous Executive should stay in the organization with another role, contact Duvo support; existing Executive roles cannot currently be changed in the app. Once the domain is claimed, colleagues who sign up with a matching email are routed to your organization instead of getting one of their own — joining immediately or submitting a join request, depending on your [discovery mode](/user-guide/organizations/organizations-overview#organization-discovery-modes). If Duvo matches someone to the wrong organization, contact Duvo support before they continue. Duvo recognizes common public webmail domains, such as Gmail and Outlook, as personal. Those addresses do not take part in domain matching and are prompted to create a standalone team instead. Other domains may be treated as work domains. Invitations have no domain restriction: an admin can invite any address, personal ones included, which is how you add contractors and consultants. ## Having Duvo set it up for you For a larger rollout, ask your Duvo contact to provision everything before anyone signs up: the organization and its discovery mode, your email domains, your nominated first admins at any role including **Executive** and **Owner**, new teams, and any standalone teams you already use moved in with their members, agents, and Connections intact. Send us the organization name, the domains to claim, and an email address and intended role for each admin — nominate at least two, so nobody is blocked when one is away. Anyone without a Duvo account yet can be invited up front and accept after signing up. ## Single sign-on If your company wants people to sign in to Duvo through your own identity provider, get in touch with us and we will walk you through the options for your organization. ## First admin checklist Whichever way your organization was created, this is the sequence to work through. Everything below lives in the **Teams**, **Members**, and **Settings** entries of the organization sidebar. In **Settings → General**, set the organization name and logo. In **Members**, invite the people who will run Duvo with you. You can only grant roles up to your own level, so appoint Owners and Executives while an Executive is doing the inviting. In **Settings → Domains**, add every work domain your colleagues use. At least one current organization member must already use each domain. For an additional domain, invite someone with that address and wait for them to join before adding it. A domain can belong to only one organization; if one is rejected as already claimed, contact Duvo support. In **Settings → Domains**, below the claimed domains, pick the discovery mode that fits your company (during onboarding the same choice is labeled **Auto-join** / **Require approval**): * **Open access** — anyone with a matching domain becomes a Member on signup. Lowest friction, best for a broad rollout. * **Request access** — every newcomer submits a join request for an admin to review. Best when you want to control adoption, or your domain is shared with people who should not have access. In **Teams**, create a team per department, function, or project — only Admins, Owners, and Executives can do this, which keeps the list curated. Rename the initial **My Team** from **Team Settings → General**. Then open **Team Settings → Team** for each team and use the **Team access** section to choose whether organization Members join directly or need approval. Set sensitive teams such as Finance to require approval. These settings do not restrict organization Admins, Owners, or Executives: they can open every team and join without approval. Let domain discovery do the work, or invite people explicitly from the **Members** page. ## Adding people Three mechanisms, and they are not interchangeable: * **Domain discovery** — the bulk of your company. Everyone arrives as a Member. * **Email invitation** — for admins, and anyone outside your email domains. You choose the role, up to your own level. * **Invite link** — for onboarding a group quickly. Always grants Member, and works for anyone holding it — it stays active until you regenerate or delete it, so do that if it spreads further than you intended. ## How admins get access to teams Admins, Owners, and Executives can open every team in the organization without joining it, so a new admin has full visibility the moment their role is set. This access is read-only until they join. When they do join a team, their team role follows their organization role: | Organization role | Team role on joining | | ----------------------- | -------------------- | | Executive | Team Administrator | | Owner | Team Owner | | Admin | Team Manager | | Member (auto-join team) | Team Member | For the full breakdown, see [Organization Roles and Permissions](/user-guide/organizations/roles-and-permissions) and [Team Roles and Permissions](/user-guide/teams/roles-and-permissions). ## Troubleshooting A domain can belong to only one organization, so **Settings → Domains** rejects it while another organization holds it — you cannot resolve this yourself. It usually means a colleague signed up before your organization claimed the domain and Duvo created one for them. Contact Duvo support: we can move the domain and their teams into the organization you want to keep. Existing teams can be moved in without losing their members, agents, or Connections, but you cannot do it yourself — ask your Duvo contact. Admin-level roles review requests on the **Members** page, which shows a badge while any are pending. If nobody is reviewing them, appoint another Admin — or switch to **Open access** if approval is not adding value. An organization must always keep at least one Executive. Appoint the new one first. The new Executive can remove the previous one if they are leaving the organization. If they should stay with another role, contact Duvo support. Check their organization role. Everyone in the organization sees every team in **Teams**, but a Member can only open the ones they have joined — the rest offer **Join team** or **Request to join** instead. Admins, Owners, and Executives can open any team without joining, with read-only access until they join. ## Related Topics What organizations are, discovery modes, and cross-team views Every organization-level permission, broken down by role How to structure teams and manage membership