Team Roles & Permissions

Team Level Roles

Owner Role

• Key responsibilities:
  • Manage team settings and configurations
  • Oversee team members and their roles
  • Make financial decisions for the team
• Access and permissions: Full control over the team, including billing information and payment methods.

Member Role

• Key responsibilities:
  • Participate in team discussions and activities
  • Contribute to projects as assigned by the owner or other members
  • Manage their own tasks and assignments
• Access and permissions: Limited access to team settings and configurations, but can view project details and collaborate with other members.

Developer Role

• Key responsibilities:
  • Develop and deploy code for projects
  • Manage project environments and settings
  • Collaborate with other developers on project development
• Access and permissions: Full control over project environments and settings, as well as access to project billing information.

Contributor Role

• Key responsibilities:
  • Contribute to specific projects as assigned by the owner or other members
  • Manage their own tasks and assignments within those projects
  • Collaborate with other contributors on project development
• Access and permissions: Limited access to team settings and configurations, but can view project details and collaborate with other contributors.

Billing Role

• Key responsibilities:
  • Oversee and manage the team's billing information
  • Review and manage team and project costs
  • Handle the team's payment methods
• Access and permissions: Full control over team billing information and payment methods, as well as read-only access to all projects within the team.

Viewer Role

• Key responsibilities:
  • Monitor and inspect all team projects
  • Review shared team resources
  • Observe team settings and configurations
• Access and permissions: Broad viewing privileges, but restricted from making changes.

Project Level Roles

Project Administrator

• Key responsibilities:
  • Govern project settings
  • Deploy to all environments
  • Manage all environment variables and oversee domains
• Access and permissions: Significant authority at the project level, but restricted to the projects they're assigned to.

Project Developer

• Key responsibilities:
  • Initiate deployments
  • Manage environment variables for development and preview environments
  • Handle project domains
• Access and permissions: Full control over project environments and settings, as well as access to project billing information.

Project Viewer

• Key responsibilities:
  • View and inspect all deployments
  • Review project settings
  • Examine environment variables across all environments and view project domains
• Access and permissions: Broad view, but restricted from making changes.