Permissions & Access
Reports, Charts, Templates, CQL & Export for Confluence uses Confluence's native permission model. No additional permission management is required - the app works within your existing Confluence access controls.
Installation Permissions
| Role | Can Install App? |
|---|---|
| Confluence Site Admin | Yes |
| Confluence Space Admin | NO - must request install from an admin |
| Regular Confluence user | NO- must request install from an admin |
Macro Usage Permissions
Once the app is installed, any Confluence user with page edit access can insert the macro.
| Action | Who Can Do It |
|---|---|
| Insert the macro on a page | Any user with Edit permission on that page |
| Configure the macro (open editor) | Any user with Edit permission on that page |
| View a published report | Any user with Read permission on the page |
| Export report data (CSV/JSON) | Any user who can view the published report |
How Report Data Visibility Works
Reports, Charts, Templates,CQL & Export for Confluence respects Confluence content restrictions when a report is built. The data in a report is scoped to what the user who builds and saves the report is permitted to access
| Scenario | Result |
|---|---|
| Report builder has access to all queried spaces | Full results displayed |
| Report builder has access to only some spaces | Only permitted content appears |
| Report builder has no access to a space | That space's content is excluded entirely |
| Page has content restrictions | Restricted pages are excluded from results |
Important: All users viewing the same report on the same page see the same results -the results saved by the person who saved the report.
Confluence Groups & Conditional Visibility
If you need to show different reports to different user groups (e.g., admins vs. contributors), use Confluence's native Page Restrictions or Space Permissions to control who can view which page. There is no app-level group configuration required.
Recommended Setup for Role-Based Reporting
- Create separate Confluence pages for different audiences (e.g., an admin dashboard page, a contributor overview page).
- Apply Confluence page restrictions to limit who can view each page.
- Insert the appropriate report macro on each page.
- Each user group sees only the report page they are permitted to access.
No Admin Panel Required
The app has no separate admin panel or settings screen. All configuration is done directly in the macro editor on each Confluence page - no special admin access is needed to configure reports.