Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
"Settings (Tenant ): display list of settings pages" (and similar) Permissions Exist When they Shouldn't
Description
Steps to repro:
Log into folio-snapshot or other environment
Go to Users and edit a user and open the permissions section and search for "Settings (Tenant): display list of settings pages" plus many other "Settings (...): display..." permissions
Expected: Permission should not be found/should not exist. We don't need permissions for just displaying lists of options as permissions should be oriented around a function you want to perform (and the necessary navigation should come along with that permission)
Actual: This permission exists. This is confusing to users because removing this permission doesn't remove the options from the UI if you have been given access to a specific function within Settings > Tenant (e.g. Settings (Tenant): Can create, edit and remove locations). The solution is to remove this unnecessary permission.
@Anya I added it to the Bug Fest 3.1 test run, therefore we're not going to lose track of it.
Anya July 25, 2019 at 9:25 PM
@Anton Emelianov should I close this ticket ... or leave it open so we remember?
Anton Emelianov July 25, 2019 at 8:42 PM
@Anya, It is good enough for now. We'll address each of these modules individually.
Anya July 25, 2019 at 8:01 PM
Edited
We are still seeing this type of permissions in non-core permissions but not in core. @Anton Emelianov , @Cate Boerema does the attached screen shot that @Ann-Marie Breaux added look correct or does there need to be more done?
Steps to repro:
Log into folio-snapshot or other environment
Go to Users and edit a user and open the permissions section and search for "Settings (Tenant): display list of settings pages" plus many other "Settings (...): display..." permissions
Expected: Permission should not be found/should not exist. We don't need permissions for just displaying lists of options as permissions should be oriented around a function you want to perform (and the necessary navigation should come along with that permission)
Actual: This permission exists. This is confusing to users because removing this permission doesn't remove the options from the UI if you have been given access to a specific function within Settings > Tenant (e.g. Settings (Tenant): Can create, edit and remove locations). The solution is to remove this unnecessary permission.