Skip to main content
Configuring Gearset permissions

Controlling what team members can do in the Gearset application

Mark Allan avatar
Written by Mark Allan
Updated this week

Note: This article concerns permissions that apply to the Gearset application. For information on permissions related to specific resources, see:

Gearset permissions allow team owners to configure whether team members can take certain actions, for example creating their own CI jobs.

Viewing your own permissions (team members)

A team member can see which permissions they have been granted on their profile page:

If a team member is not allowed to perform an action due to lacking permission, they will see a message similar to this:

Assigning permissions (team owners)

A team owner can configure which permissions are assigned to the whole team on the Gearset Permissions page:

To restrict permissions to only some team members, assign permissions to roles. Note that permissions are additive, so if a permission is assigned to the whole team then this will override the setting at the role or user level.

Available permissions

The set of Gearset permissions currently available is as follows:

  • Add Own Org Connection

    Team members can create their own org connections.

  • Administer Gearset Templates

    Team members can create, edit or delete Gearset data deployment templates (read more)

  • Administer SCA Rules

    Team members can customise or adjust the static code analysis rules for deployments (read more)

  • Create API Personal Access Token

    Team members can create new API personal access tokens (read more)

  • Create CI Job

    Team members can create their own CI jobs (read more)

  • Create Monitoring Jobs

    Team members can set up jobs that monitor changes across environments (read more)

  • Create Pipelines

    Team members can create their own pipelines (read more)

  • Create Unit Tests

    Team members can create new unit testing jobs in order to validate code functionality (read more)

  • Download deployment packages

    Team members can download deployment packages from the deployment history page (read more)

  • Reauth Own Sandbox
    Team members can reauthorize dev sandboxes that are assigned to them after a refresh (read more)

  • Run Comparison with Local Files

    Team members can select Local Files as a comparison source location in Compare and Deploy (read more)

Did this answer your question?