Skip to main content

User roles on project teams

Abstract

Bitrise apps have user roles defined on their team. They limit what you can and cannot do with an application. The same user can have different roles on different projects.

Roles provide access control on Bitrise: they limit what actions a user can and cannot perform on a Bitrise project.

Roles work on an project basis: the same user can have different roles on different applications.

Workspace members - both viewers and managers - can be assigned to a project’s team either individually or in a Workspace group.

There are four types of roles that you can assign to a user on a project's team:

In addition, each project has Owners.

Owners

Bitrise projects are owned by Workspaces. On the project's team, users who are owners in the Workspace have the owner access right to the project.

Owners have unlimited access to projects. Only owners can destroy projects or transfer the ownership of projects, and only they have access to payment information.

Admins

Here’s the role cheatsheet for admins of a project's team:

admin-role.png

An admin cannot delete a project but can invite other members to work on the project. The admin can also give admin rights to other users. However, they cannot transfer ownership of the project: only Owners can do that.

Release manager role

Admins are also granted the Release manager role by default. They can also grant Release manager acccess to other users: Granting Release manager rights.

Developers

Here’s the role cheatsheet for developers:

developers-role.png

Developers cannot change team member roles, add new team members, remove existing team members or create, edit or delete Workflows. They can, however, run builds and view build logs.

They have no access to sensitive data such as payment information, access tokens or even webhooks.

Platform Engineers

Here's the role cheatsheet for Platform Engineers:

plateng-role.png

Platform Engineers can do everything that Developers can, and in addition to that, they can also edit Workflows. They can't access the project settings, manage team members or billing, and they can't delete the project.

Testers/QA

Here’s the role cheatsheet for testers/QA:

tester-qa-role.png

Testers can only view builds. They cannot access build logs and they cannot modify the project in any way or form.

They have no access to sensitive data such as payment information, access tokens or even webhooks.