Current manifest scopes
permissions:
scopes:
- read:jira-user
- read:jira-work
- read:project:jira
- read:board-scope:jira-software
- read:board-scope.admin:jira-software
- read:sprint:jira-software
- read:issue-details:jira
- read:jql:jira
- read:user:jira
- storage:app
- read:space:confluence
- read:page:confluence
- write:page:confluence
- read:content-details:confluence
- write:attachment:confluenceScope purposes
| Scope | Purpose |
|---|---|
read:jira-user | Read authorised Jira user display information needed for assignee-oriented reporting. |
read:jira-work | Read Jira work items and related fields used by Sprint and Project/Program reporting. |
read:project:jira | List and identify Jira projects available to the current user. |
read:board-scope:jira-software | Read Jira Software board information used for board selection and reporting context. |
read:board-scope.admin:jira-software | Read board-level configuration needed for reporting/estimation context where Jira exposes it through board administration APIs. |
read:sprint:jira-software | Read Sprint names, dates, goals, state and related Sprint information. |
read:issue-details:jira | Read authorised issue-level detail used in reports, calculations and exports. |
read:jql:jira | Run authorised Jira searches required for reporting and Custom Jira Insights. |
read:user:jira | Read authorised Jira user details such as display names used in reports. |
storage:app | Store short-lived caches plus reporting settings, commentary overlays, schedules, publication metadata and fair-use counters in Atlassian-hosted Forge storage. |
read:space:confluence | List/read Confluence spaces available to the current user for the explicit publishing destination selector. |
read:page:confluence | Read accessible Confluence pages so the user can choose a parent/report page and StatusDeck can determine create/update behaviour. |
write:page:confluence | Create or update the report page when the user explicitly selects Publish to Confluence. |
read:content-details:confluence | Read Confluence content metadata needed for publication/version handling. |
write:attachment:confluence | Attach or update the generated PDF, PowerPoint and supported visual assets on the selected Confluence report page. |
Jira remains read-focused
The current manifest does not request Jira write scopes. StatusDeck does not use these permissions to edit Jira issues, projects, boards or Sprints.
Why Confluence write scopes exist
Confluence write permissions are used only for the explicit report-publishing workflow initiated by the user. They allow StatusDeck to create/update a report page and its attachments. Confluence is optional in the app compatibility configuration.
User-context enforcement
StatusDeck uses Atlassian user-context access for Jira and the Confluence publishing workflow. Atlassian product permissions continue to determine what Jira/Confluence content the current user can read or modify.
Scope changes
QTI Labs reviews and minimises requested scopes. Material additions are documented and may require administrator re-consent through Atlassian.
Documentation baseline: 3 September 2026. This documentation describes the current submitted StatusDeck capability set and is updated when material product, permission, storage or security behaviour changes.