Permissions & roles

Exportelier is permission-first: every operation begins with a permission check, and exports never reveal data a user could not already see.

Exports run as the user

When you export, the operation runs as you. You can only include issues you are allowed to browse in Jira. There is no way to use Exportelier to see restricted issues.

Admin-only template management

Creating and editing templates is restricted to administrators. Regular users select from available templates at export time but cannot modify them.

The admin area showing template management restricted to administrators.

Reports: admin builds, everyone exports

Reports follow the same split, one level up:

Action	Site admin	Any authenticated Jira user
See the report list	✅	✅
Export an enabled report	✅	✅
Create, edit, duplicate, delete a report	✅	—
Open the report designer, manage data sources	✅	—

Administrative actions are enforced in the resolver, not merely hidden in the UI, so calling them directly does not bypass the check.

Building a report is not sharing its data

A site admin adds Saved Filters that they can see. That never widens what anyone else receives: each export re-reads every filter as the exporting user. If a filter is not shared with that person, their export fails and names the source instead of returning a smaller document. Share the Saved Filter in Jira to grant access — Exportelier deliberately offers no way around Jira's own sharing.

Dashboard import: admin only, and never wider than Jira

Importing a Jira dashboard, checking it for changes, and re-importing it are site admin actions.

Every dashboard, gadget and Saved Filter read during an import runs as the admin performing it, so Exportelier can only import dashboards Jira already shows that person. A dashboard that is not shared with them is neither listed nor reachable by pasting its id.

That visibility applies at import time only. Once the report exists, every export re-reads its filters as whoever exports it, exactly like any other report — so importing a dashboard never grants anyone access to data they could not already see.

Future role-based access

Role-based access (for example, Editor vs. User) is a deferred roadmap idea without a committed release or edition. Template management remains admin-only.

Granting and revoking access

Access follows Jira permissions and the app's roles. Review them when onboarding or offboarding team members.