Roles and permissions
In Bitrise Release Management, users have permissions based on workspace-level roles and project-level roles. Each role has its own set of permissions. Workspace owners and project admins can manage most aspects of a Release Management app.
To perform actions in Release Management , your account must have the required access. This access is controlled by permissions. A permission is the ability to perform a specific action, such as adding and connecting apps, creating releases, or changing connected app settings.
Roles and permissions overview
You can assign different roles to different team members. In Release Management, there are five different roles on three different levels:
-
Workspace-level roles: These roles aren't tied to a specific Release Management app, nor can you change them in Release Management. They are fully tied to the Workspace that owns the Bitrise project that the connected app belongs to. There are two Workspace-level roles:
-
Workspace owner: Workspace owners have full administrative control over all aspects of an app in Release Management, without any limits or exceptions.
-
Workspace manager: The main purpose of workspace managers is to manage workspace collaboration. In Release Management, they can add a new app when creating a new project. They, however, can't add a new RM app under an already existing project.
-
Contributor and Viewer: These Workspace-level roles have no default access to Release Management apps.
-
-
Project Admin: The only project-level role in Release Management. Adding a user to a project doesn't automatically give them any permissions in Release Management, with the exception of users with the Admin role. Project Admins have full administrative rights to apps, builds, Release Management, and app deployment with one exception: the Project Admin cannot add a new app with a new project to Release Management. When adding a new app to Release Management, they can only add it under the project of which they are admin.
-
Release Management-level roles: These are the roles you can configure within Release Management.
-
Release manager: The main purpose of Release Managers is to handle releases to online stores. They can't add new apps or access app settings.
-
App tester: The App tester role is meant for internal testers. They can access an app and its artifacts, and the build distribution and tester groups menu. They have no other access.
-
Roles and permissions for Release Management apps
|
Actions |
Workspace owner |
Workspace manager |
Project admin |
Release manager |
App tester |
|---|---|---|---|---|---|
|
Access all apps of a project |
|
|
|||
|
Access a specific app |
|
|
|
|
|
|
Access app settings and integrations |
|
|
|||
|
Access release presets |
|
|
|||
|
Access artifacts |
|
|
|
|
|
|
Access the list of release managers |
|
|
|
||
|
Access feature flags |
|
|
|||
|
Add a new app to RM with a new project |
|
|
|||
|
Add a new app to RM with an existing project |
|
|
|||
|
Remove an app from RM |
|
|
|||
|
Assign a license to an app |
|
|
|||
|
Create, edit, and delete:
|
|
|
|||
|
Upload artifacts |
|
|
|
Roles and permissions for build distribution and releases
|
Action |
Workspace owner |
Workspace manager |
Project admin |
Release manager |
App tester |
|---|---|---|---|---|---|
|
Access the build distribution menu |
|
|
|
|
|
|
Access the tester groups |
|
|
|
|
|
|
Access the list of testers |
|
|
|||
|
Enable the public install page |
|
|
|||
|
Create, modify, and notify tester groups |
|
|
|||
|
Update, approve, and delete assigned tasks |
|
|
|||
|
Create, modify, pause, and delete releases |
|
|
|
||
|
Create and modify store version and localization |
|
|
|
||
|
Submit release for review |
|
|
|