Permissions and scopes

Cloud Scheduler follows a least-privilege approach and uses Jira permission context. Access to Jira data depends on Jira permissions, the user context and the scopes granted during installation.

Documented scopes

• read:jira-work — read Jira work data required for planning.
• write:jira-work — create or update Jira work-related data where enabled by product features.
• read:jira-user — read Jira user information required for resource planning.
• storage:app — store app configuration, resource groups and planning data in Forge Storage.

Permission expectations

• The app should not request Atlassian passwords or login credentials.
• The app should not bypass Jira project permissions.
• Any future scope change should be documented in the Marketplace listing and this documentation.