Skip to content

Roles and access

Access combines app permissions, program roles, assignments, and current Jira/JSM visibility. Being an app administrator does not make private review content visible.

Role What it enables
Jira or app administrator Manage app access, diagnostics, and supported data-erasure controls. Private review content still requires the appropriate program access and current source permissions.
Program creator Create a program and become its first manager. This does not grant access to other programs.
Program manager Configure the program, manage participation, prepare periods, assign reviews, and follow up on authorized results.
Reviewer Complete eligible assigned reviews and participate in assigned calibration exercises.
Read-only stakeholder Read authorized program information without making review judgments or managing the program.
Reviewed agent Be included in a program's reviewed-agent roster. This role alone does not expose the underlying private review.
Coaching recipient Read the separate summary a manager has deliberately released to them in My coaching.

Jira access remains necessary

Adding someone to a program does not grant Jira permissions. Content based on a request or comment remains subject to current source access. If access cannot be verified, affected content is withheld.

Reports containing only outcome numbers and completed-results CSV use current issue visibility. They do not include cited comment text. See Results and exports.

Assignment is separate from membership

A reviewer needs a valid assignment and an open review, as well as membership and Jira access. They may need to confirm that they did not handle the ticket. Self-review is blocked.

If you can open the app but cannot see a program or review, ask a manager to check your role, assignment, and underlying Jira access. Do not use another person's account to work around a restriction.