- Log in as an administrator into JIRA
- Go to Manage Add-ons to Configure Dashboard Folders for JIRA, or use the shortcut 'g'+'g' and type in "Dashboard Folders"
- Admin will see the Dashboard Folders listing page
- Click on the "Edit Folder Permission" button (the button will only appear if there are Folders created – see How to Create and Edit Dashboard Folders)
- Select the Permission Type:
- Private: Folder will not be shared to any user, only administrators can see it (default setting)
- Public: Folder will be visible to everyone, including user's not logged in
- Logged in Users: Folder will be visible to all logged in users
- Shared to Group/Project: Folder will be visible to the specified Group(s) / Project Role(s)
- Select the Folder on the left to apply the "Selected Permission(s)" to the Folder
- Click on the "Update Permission" button to update the "Selected Permission(s)" to the targeted Folder
- Click on "Save Permission" to save the sharing permission on the selected Folders
Cascading Permission
The Folder permission is governed by the parent Folders.
I.e. if a user does not have permission to see the top folder, then all subsequent folders nested inside this top folder will not be visible to the user
Folder Permission
Folder Permission ≠ Dashboard Permission
The user might have permission to see the Folder (and it's encapsulated Dashboard links), but the Dashboard's own permission will still be adhered to
To ensure that the users can see the Dashboard normally, ensure that:
- Dashboard itself is shared to the user
- Filters used by the Gadgets is shared to the user
- the user has Browse Permission to the Project
Public Permission
The Public permission set to the Folder only allows the anonymous users to see the Dashboard links from the top navigation bar, but anonymous users might still be unable to view the Dashboard.
To allow anonymous to view the Dashboard, ensure that:
- The Dashboard itself is shared to "Everyone"
- The Filters used by the Gadgets is shared to "Everyone"
- The Gadget supports not logged in access
- The Project itself has Browse Permission set to Group: "Anyone"