Set Promote and Release Permissions

Configure JFrog AppTrust Promote and Release permissions on global or project roles to control who can promote versions through stages or release to production.

JFrog AppTrust uses separate permissions for promoting and releasing application versions. This allows you to control who can promote a version through non-production stages (such as DEV or QA) independently of who can release a version to production.

The permissions are:

  • Promote: Grants the ability to promote an application version to a non-production stage. The permission is stage-aware, meaning you can scope it to specific stages in the lifecycle.
  • Release: Grants the ability to release an application version to the production stage. This permission is evaluated separately from Promote.

These permissions are independent. A user can have Promote only, Release only, both, or neither. For example, you might grant a developer permission to promote versions through DEV and QA stages but not to release to production, while a release manager might have both. You can further scope the permissions for promotion. For example, you could allow a user to promote to DEV only, a second user to promote to QA and STAGE, and a third user to release to PROD.

Promote and Release permissions may be defined using global or project-level roles. You can follow the same Application Versions actions in a project role when you manage permissions inside a project. This procedure shows an example using a Global Role.

Setting the permissions requires the following main parts:

  • Create Role: Create one or more roles that include the desired Promote and/or Release permissions.
  • Associate User: Assign the required role to the user.

These parts are included in the procedure below.

Prerequisites

  • Administrator permissions to manage roles in the JFrog Platform and familiarity with user management.
  • The relevant global and/or project lifecycle stages defined.
  • An AppTrust user already created, but without the Promote or Release permissions defined yet.
  • A role that includes the Write Artifact permission.

To set up Promote and Release permissions:

  1. In the JFrog Platform, set the project to All Projects.

  2. Go to Administration > Global Roles > Create Global Role.

  1. Complete the following:

    • Role Name: Enter a name describing the role, for example, DEV and QA promoter.
    • Global Environments: From the dropdown, choose the stages this role can promote to, for example, DEV and QA. For a global role, you can only choose global stages.
    • Actions, Artifacts: Mark Write Artifacts, if it is not marked already.
  2. Click Advanced, and scroll down until you see Application Versions. Choose the relevant permissions. For this example, mark Promote. Ensure that Release is unmarked. To grant release access instead, mark Release and include the release stage (PROD by default) in the role environments.

  1. Click Create. The new role appears in the list of roles.

  2. Choose the project where the user is a member. If you have to add the user to a project, do that now.

  3. Go to Administration > Members.

  4. Locate the relevant project member and click in the Roles column. The list of roles opens.

  1. In the list, mark the new role, for example, DEV & QA promoter. The user now has permission to promote an application version to the DEV and QA stages only.

Frequently Asked Questions

This section provides answers to frequently asked questions.

plusFAQs
Q: What is the difference between Promote and Release permissions?

A: Promote allows promotion to non-production stages you scope on the role. Release allows releasing an application version to the production (release) stage. The actions are PROMOTE_APPLICATION_VERSION and RELEASE_APPLICATION_VERSION.

Q: Why do I need Write Artifacts?

A: Promote and release operations write artifacts in target repositories unless you use Keep Artifacts. Include Write Artifacts on the role so those operations can complete. See Prerequisites.

Q: Can I use a project role instead of a global role?

A: Yes. Promote and Release can be set on global or project-level roles. This procedure uses a Global Role as the example. See Prerequisites.

Q: How do I grant permission to release to PROD?

A: On the role, mark Release under Application Versions and include the release stage (PROD by default) in the role environments. Assign that role to the project member as described in the procedure on this page.

Related Topics


Did this page help you?