.png){kind=logo}
Project User Access
Overview
Each Jira project has a Project Access Review page for project admins to review the list of users who has Browse/Admin access to the project.
Out of the box, project admins are unable to perform this because only Jira admins can see the members of Jira groups granted access.
Project admins can use this page to
review the users who
add notes on project users
export the list of users who has access
update the last review date for compliance tracking
Access to projects should be reviewed periodically by Jira project administrators.
Accessing the review page
You can find a list of users who have browse or admin access under Project Access Review.
The review page can be assessed from Project Setting → Apps → Project Access Review
How to use the Review Page
Steps
Read the Information Panel
Take a look at the user list in the table below
Green lozenges indicate admins
There is a grey lozenge on each product access
Review the roles and permissions for having browse permissions
(Optional) In preparation for the next review, add a note explaining why the user requires access to the project
Remove those users who should not have access to this project
Once completed, click on Review button
Features in Page
Feature ⭐ | Description | Challenge Addressed | |
|---|---|---|---|
| 1 | Display the list of users with browse access | Show who has browse permission to the project and explain how the access was granted | Difficult and tedious to correlate between project role and associated permission scheme |
| 2 | Project Admin Lozenges | Highlight users who have admin access | Project Admin access is higher risk because they can modify the permissions |
| 3 | Enumerating the members of groups in role | List down who are the members of that group instead of showing the group names | Only Jira admins can see who is in the group |
| 4 | Assigned product license lozenges | Facilitate troubleshooting by showing the licenses assigned to the user | Users with browse permission cannot access if they do not have an assigned license |
| 5 | Editable notes on user | Can add notes on why a user was granted access to the project and facilitate collaboration among multiple project admins | It is tough for a project admin to know everyone in a large project |
| 6 | Searching by user/project roles | Save time on searching for a very long list | Facilitates transfer to role to another |
| 7 | User List Export | Take a current snapshot of access granted | Export user list is not available by default |
| 8 | Last Review Date | When is the project due for another review? | Project admin needs to remember when the next review date is |
| 9 | Last Reviewed By | Has the review been done by another project admin? | The info is captured directly in the Jira project (with context and easily accessible) |