Skip to main content

User roles on app 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 apps.

Roles are very important on Bitrise. They limit what actions a user can and cannot perform on an application.

Roles work on an app basis: the same user can have different roles on different applications. As such, Workspaces have no inherent roles, apart from that of the Workspace owners: Workspaces have groups and different groups can be assigned different roles on an app's team.

Owners

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

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

Admins

Here’s the role cheatsheet for admins of an app's team:

Admin_role_csheet.png

An admin cannot delete an app but can invite other members to work on the app. The admin can also give admin rights to other users - however, they cannot transfer ownership of the app!

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:

Developer_role_csheet.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.

Testers/QA

Here’s the role cheatsheet for testers/QA:

Testers_QA_role_chseet.png

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

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