Permissions & Access
How Access Works
Dashboard Templates, Charts, Graphs & Reports for Jira does not have its own user role system. Access is governed entirely by Jira's existing permissions:
| Access Level | How It's Determined | What Users Can Do |
|---|---|---|
| Dashboard Owner / Editor | Jira dashboard share permissions | Add, edit, and remove gadgets; save configurations |
| Dashboard Viewer | Jira dashboard share permissions | View gadget data; use Dynamic Filter Controller filters, quick filters, chart/table toggles, and export if enabled |
| Jira Admin | Holds the global Administer Jira permission | Access Admin Settings; enable/disable features and data sources |
Jira Dashboard Permissions
Gadget access is tied to Jira dashboard permissions:
| Permission | Who Sets It | Effect |
|---|---|---|
| Owner | Dashboard creator | Full edit access |
| Can Edit | Dashboard owner shares with individuals or groups | Can add/edit/remove gadgets |
| Can View | Dashboard owner shares with individuals or groups | View-only; can interact with filters but not edit gadgets |
To share a dashboard: open the dashboard → click Actions (•••) → Share → add users or groups.
Data Access (What Charts Can Show)
Charts and tables only show Jira data the current user can see. If a user does not have "Browse Projects" permission for a project, issues from that project will not appear in their charts - even if the gadget is configured with that project as a source.
This means:
- Sensitive projects are automatically excluded for users without access
- No special configuration is needed to enforce data security
- Jira's native permissions are the single source of truth
Two people looking at the same gadget can therefore see different numbers, and that is correct behaviour - each is seeing their own permitted slice of the data.
What the App Stores
The app stores gadget configurations only - chart type, selected fields, column choices, and display options - in Forge storage inside your own Atlassian site. No Jira issue data is copied, cached outside Jira, or sent anywhere else. Every Jira request is made as the signed-in user, which is what makes the permission behaviour above automatic rather than something an admin has to configure.
Admin Settings Access
Admin Settings are only accessible to users who hold the global Administer Jira permission. Project administrators do not have access. Regular users cannot change global export settings, feature toggles, or data source restrictions.
To open Admin Settings:
- Log in as a Jira administrator
- Go to Apps in the top navigation
- Open Dashboard Templates, Charts, Graphs & Reports for Jira
- Click the Admin page
When an Admin Restricts Something
Admin Settings can switch gadgets, data sources, and export off across the whole site. This is what users see when that happens:
| What the admin changed | What the user sees |
|---|---|
| A gadget is turned off in Admin → Features | Existing gadgets of that type stay on the dashboard but show a notice instead of the report |
| A data source is turned off in Admin → Data Sources | That source disappears from the gadget's source selector. A gadget already using it shows This data source is turned off instead of its data, and in edit mode Save is disabled until another source is chosen |
| Export is turned off in Admin → Customization Options | PNG, PDF, and CSV options are hidden from every gadget's menu |
None of these delete anything. Re-enabling the setting restores the gadget exactly as it was, with its configuration intact.
How to Request Access to a Dashboard
If a dashboard is not shared with you:
- Contact the dashboard owner (shown in the dashboard header)
- Ask them to share the dashboard with your Jira user or group
- The owner can set view or edit permissions
There is no self-service request form - access is granted by the dashboard owner.
Gadget Export Permissions
If export buttons (PNG, PDF, CSV) are missing or disabled:
- Check with your Jira admin - export may be disabled globally in Admin Settings
- The admin can re-enable it under Admin → Customization Options → Allow direct export