---
title: Project Level Roles
product: vercel
url: /docs/rbac/access-roles/project-level-roles
canonical_url: "https://vercel.com/docs/rbac/access-roles/project-level-roles"
last_updated: 2026-07-01
type: reference
prerequisites:
  - /docs/rbac/access-roles
  - /docs/rbac
related:
  - /docs/rbac/access-roles
summary: Learn about the project level roles and their permissions.
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

# Project Level Roles

> **🔒 Permissions Required**: Project level roles


<!-- docsgraph:related -->
## Related pages

> **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below.

- [How do I transfer ownership of a Vercel team?](https://vercel.com/kb/guide/how-do-i-transfer-ownership-of-a-vercel-team?from=related) — Learn how to transfer ownership of a Vercel team, including the exact dashboard steps to promote a new Owner and remove
- [Team Level Roles](https://vercel.com/docs/rbac/access-roles/team-level-roles?from=related) — Learn about the different team level roles and the permissions they provide.
- [Extended Permissions](https://vercel.com/docs/rbac/access-roles/extended-permissions?from=related) — Learn about extended permissions in Vercel's RBAC system. Understand how to combine roles and permissions for precise ac
- [Managing Team Members](https://vercel.com/docs/rbac/managing-team-members?from=related) — Learn how to manage team members on Vercel, and how to assign roles to each member with role-based access control \(RBAC
- [Access Groups](https://vercel.com/docs/rbac/access-groups?from=related) — Learn how to configure access groups for team members on a Vercel account.
- [Permissions and Access](https://vercel.com/docs/integrations/install-an-integration/manage-integrations-reference?from=related) — Learn how to manage project access and added products for your integrations.

Full cross-link map for this page: [/docs/rbac/access-roles/project-level-roles.graph.md](/docs/rbac/access-roles/project-level-roles.graph.md)
<!-- /docsgraph:related -->

Project level roles are assigned to a team member on a project level. This means that the role is only valid for the project it is assigned to. The role is not valid for other projects in the team.

## Equivalency roles

In the table below, the relationship between team and project roles is indicated by the column headers. For example, the team role "Developer" is equivalent to the "Project Developer" role.

- The [**Developer**](/docs/rbac/access-roles#developer-role) team role is equivalent to the [**Project Developer**](/docs/rbac/access-roles#project-developer) role
- The [**Viewer Pro**](/docs/rbac/access-roles#pro-viewer-role), [**Viewer Enterprise**](/docs/rbac/access-roles#enterprise-viewer-role), and [**Billing**](/docs/rbac/access-roles#billing-role) team roles are equivalent to the [**Project Viewer**](/docs/rbac/access-roles#project-viewer) role
- The [**Owner**](/docs/rbac/access-roles#owner-role) and [**Member**](/docs/rbac/access-roles#member-role) team roles are equivalent to the [**Project Admin**](/docs/rbac/access-roles#project-administrators) role

All project level roles can be assigned to those with the [**Contributor**](/docs/rbac/access-roles#team-level-roles) team role.

See our [Access roles docs](/docs/rbac/access-roles) for a more comprehensive breakdown of the different roles.

## Project level permissions


---

[View full sitemap](/docs/sitemap)