Team Members and Roles are available on Pro and Enterprise plans
Teams are made up of members, and each member of a team can be assigned a role. These roles define what you can and cannot do within a team on Vercel.
As your project scales and you add more team members, you can assign them roles to ensure that they have the right permissions to work on your projects.
Vercel offers a range of roles for your team members. When deciding what role a member should have on your team, consider the following:
- What projects does this team member need to access?
- What actions does this team member need to perform on these projects?
- What actions does this team member need to perform on the team itself?
See the Managing team roles section for more information.
To invite new members to your team, select the team from the scope selector, then open the Settings tab and select the Members section.
Enter the email address of the person you would like to invite, select their role, and click the "Invite" button. You can invite multiple people at once via the "Add more" button.
As the team owner, you can add new members, remove existing members, and change their roles.
Members who have accepted an invitation to the team will be displayed as Team Members with their assigned roles.
An invite link can be generated from the Members section of the Settings tab. This link can be shared with others to allow them to join the team without needing to be invited individually. This link can be reset to limit people from sending requests to join the team.
If you are interested in joining one of the Suggested Teams, then you can request access to join.
The team owner can accept, decline or change role permissions for your request from the Pending Invitations list. You can click the “Leave Team” button accessible via the ellipsis next to your Team role to Leave a Team.
Team Members can be assigned roles that grant them permission to perform certain actions. Once added, these members get different levels of access for all the projects under the scope of that team.
These roles have specific Role-based access control (RBAC) permissions depending on your team's plan: Pro or Enterprise.
There are two roles for team members on a Pro team plan:
The owner role is available on Pro and Enterprise plans
Team owners have admin-level access to the entire team. A team owner can edit and manage all project settings, from creating and previewing deployments to promoting them to production, as well as editing and managing security, billing, and Git settings. You can also use the "Add New" drop-down menu to perform quick tasks like adding Projects, Domains, or Team Members.
Teams can have more than one owner. To maintain ownership continuity for your team, you should have at least two people with owner permissions. Adding additional owners will not remove any existing ownership.
Note that only those with the owner role can change other team members roles.
Team owners can also manage Environment Variables in all Environments and change the roles of other members on the team — including other owners. The only way to remove oneself as an owner is by either leaving or deleting the team.
The member role is available on Pro and Enterprise plans
Those with a member role can create deployments, manage projects, set up integrations, and manage domains for projects on a team.
The member role can manage Deploy Hooks, Serverless Function settings, and security settings for projects. However, they cannot edit any team settings, including billing information and inviting additional users to the team.
Manage Deploy Hooks
Manage Serverless Functions
Manage Security Settings
Manage Team Members
Manage Team Settings
Does your team need greater role-based access control?
With Enterprise, you can assign additional roles
For teams on the Enterprise plan, Vercel offers three additional roles:
The developer role is available on Enterprise plans
Team members with a Developer role can create deployments, manage environment variables for preview and development environments, and manage project domains on a team.
They cannot edit any team settings, including billing information and inviting additional users to the team. The developer role can also be promoted to Project Administrator on a specific project.
Users assigned with a developer role can only initiate a build when they commit to the main branch of a project if they are promoted to the Project Administrator role. However, starting December 5, 2022, a developer role can initiate a build when committing to the main branch of a Git project. This change ensures closer alignment with the security controls in your git environment.
Team owners can assign users with the developer role as administrators on any project on a team. A developer role, when promoted to a project administrator, will be able to perform admin-level actions like creating production deployments, managing all project settings, and managing production environment variables.
Manage Environment Variables in Preview and Development Environments
Create Production Deployments
Promote a deployment to production from the dashboard or via source control integrations
Manage Team Settings
Manage Project Settings
Promoting a team member as a project administrator only applies to the specific project to which the role was assigned. It does not apply to other projects on the team.
To assign the administrator role, go to the project's settings page and click the administrators tab on the left navigation bar.
Next, type the email address of the team member with the developer role that you would like to make an administrator. You can add multiple email addresses by clicking the "Add more" button. When finished, click the "Add" button.
The billing role is available on Enterprise plans
The billing role allows members to manage billing settings and invoices for a team. The billing role provides read-only access to all projects on a team. Team members assigned this role are unable to edit any project settings.
The viewer role is available on Enterprise plans
The viewer role gives read-only access to a team and prevents users from editing any team or project settings. Team members with the viewer role cannot create deployments.
The following table outlines the permissions for each role.