--- title: Enterprise description: Learn how to manage v0 seats, access, and more in your Vercel Enterprise account. docs_index: /docs/llms.txt lastUpdated: 2026-10-13 product: v0 type: guide related: - /docs/teams - /docs/security - /docs/account --- > For an index of all documentation, see [/docs/llms.txt](/docs/llms.txt). ## Managing seats and access To manage v0 seats and grant access in your Vercel account, follow these steps. 1. Log in to your [v0 account](https://v0.app). 2. Select your team from the scope selector on the top-left corner. 3. Click on the scope selector again and select **Manage Members**. This navigates you to your Vercel team's members page. You can grant v0 access to team members by clicking the three dots to the right of their role and selecting **Manage v0 role**. ### Assign or revoke access - To assign access: Find the team member in the list and assign the desired v0 role. - To revoke access: Find the team member in the list and choose "No v0 access". ### Choosing the right role v0 has a role and access control system that is separate from your team roles in Vercel: - **v0 Builder**: v0 Creator access + can create deployments and manage environment variables on any Vercel project that's connected to v0. - **v0 Creator**: Can create chats + projects, add sources, and build in v0. - **v0 Viewer**: View-only access to collaborate on chats with other users. > v0 roles control actions performed in the v0 web app. Actions performed > through other interfaces use the member's Vercel role and project > permissions instead. For example, a Vercel Viewer with the v0 Builder role > can publish from v0, but cannot deploy through GitHub or the Vercel CLI. > The v0 Builder role is **team-wide**: a Builder can create deployments and > manage environment variables on **every** Vercel project in the team that > is connected to v0, not only projects they were explicitly added to. > Assign v0 Builder only to users who should be able to act on all v0-connected > projects in the team. Note: Managing integrations requires the **Integrations Manager** permission, which is a separate team-level permission that can be selected separately when assigning members a v0 role. Members with the Vercel **Member** role inherently have this permission. To prevent integration access, assign the **Viewer** role on Vercel alongside the desired v0 role without **Integration Manager** selected. For Vercel team management: - **Viewer**: Assign the Viewer role with v0 access for most users. - **Owner**: Use the Owner role only for admins who need full control. [Read the Vercel docs to learn how to manage user permissions at a more granular level](https://vercel.com/docs/rbac/access-roles) ## Activating your account To use v0 with your Enterprise plan: Make sure you're logged into the correct Vercel account before accepting the invite. 1. Accept the invite. 2. Switch to your Enterprise team on the v0 navigation bar. ## Configuring single sign-on (SSO) Once v0 is enabled for your team, **admins** can manage access using [Directory Sync](https://vercel.com/docs/directory-sync) and [Access Groups](https://vercel.com/docs/rbac/access-groups) to provision v0 roles from your identity provider (IdP). 1. Create an **Access Group** with a v0 role from your from your team's [Access Group settings](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fsettings%2Faccess-groups\&title=Manage+Access+Groups). 2. Map a **Directory Sync** group (e.g. from Okta SCIM) to the Access Group you created. 3. Everyone in the synced group will automatically receive the v0 access configured in that Access Group. ### Configure Team Access and v0 roles in one Access Group You can assign **Team roles**, **Team permissions**, **Project roles**, and **v0 roles** in the same **Access Group** so that a single **IdP group** grants both team and v0 permissions. Team access defined within an Access Group applies when the Access Group is managed via **Directory Sync**. 1. Create an Access Group from your from your team's [Access Group settings](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fsettings%2Faccess-groups\&title=Manage+Access+Groups). Specify the required **Team Access** and **v0 Roles**. 2. Map your IdP group to this Access Group via Directory Sync. Members mapped to the group default to **Contributor** unless another mapping assigns a different Team role. 3. All members in the synced group will automatically receive the v0 access and team role configured in the Access Group. [Learn more about Access Groups in Vercel](https://vercel.com/docs/rbac/access-groups) [Learn more about v0's enterprise security features](/docs/security#enterprise-security-features) ## Custom model access The updated [model picker](/docs/model-picker) is available to Enterprise teams. Enterprise teams start with access to v0 models. Members can browse custom models from the AI Gateway catalog, but those models stay locked until a team owner enables them. ### Allow custom models 1. Switch to your Enterprise team using the scope selector. 2. Open [Workspace settings](https://v0.app/settings/workspace). 3. As a team **Owner**, turn on **Allow custom models**. Enabling this setting accepts custom models for your team, including future releases. Members can then add available custom models from **Add models** in the model picker. Individual model restrictions still apply. Only a team owner can change this setting. A v0 Builder or Creator role alone does not grant permission to enable custom models. To restrict the team to v0 models again, turn off **Allow custom models**. > Existing Enterprise teams also require owner acceptance. A previous choice to > turn off **Restrict to v0 Models** does not automatically opt the team into > custom models. Workspaces with isolated tenant restrictions remain limited to > their supported v0 models. ## Privacy settings ### Chats Members can control chat visibility using **Only people with access**, **Everyone at \[team-name]**, **Anyone with the link**, or **Anyone on the web**. Owners on v0 Enterprise teams can disable the **Anyone with the link** and **Anyone on the web** options using the **Restrict Chat Sharing** setting in [workspace settings](https://v0.app/settings/workspace). - **Only people with access**: Only the chat owner and individually invited team members can access the chat. - **Everyone at \[team-name]**: Makes the chat available to the entire team. Turn on **View only** to prevent team members from editing it. - **Anyone with the link**: Anyone with the URL can access the chat. It will not be indexed by search engines. - **Anyone on the web**: Anyone can view the chat. It may be indexed by search engines and appear in public galleries. > Members with the Vercel **Owner** team role can view, edit, and archive every chat owned by the team, including teammate chats set to **Only people with access**, when they navigate to the chat directly. This is administrative access and is not surfaced in listings — Owners only see teammate chats they open by URL. See [Team Owner access](/docs/sharing#team-owner-access) for details. Team members can also be added to the chat individually. Use this with **Only people with access** to configure chats that only a subset of team members can access. --- For a semantic overview of all documentation, see [/docs/sitemap.md](/docs/sitemap.md) For an index of all available documentation, see [/docs/llms.txt](/docs/llms.txt) For agent-facing discovery, including API and MCP surfaces, see [/docs/agents.md](/docs/agents.md)