Permissions and Data Scope
Simple Decision Log runs on Atlassian Forge inside Atlassian infrastructure.
Required permissions
The app requests Jira and Forge scopes needed to log decisions and connect them to issues.
| Scope | Why it is needed |
|---|---|
storage:app | Store decision records in Forge app storage |
Jira read scopes (for example read:jira-work) | Read project and issue data for linking and display |
Jira write scopes (for example write:jira-work) | Support issue integration features in Jira UI |
Exact scope names may vary by app version and Marketplace listing.
Data scope and isolation
- Decision data is scoped to your Jira site (tenant)
- Access follows Jira project permissions
- Users without project access cannot view project decisions
What data is typically stored
- Decision fields (title, date, status, rationale, category)
- DACI assignments
- Impact records
- Linked issue references
- Timeline/history metadata
Privacy basics
- Data is handled within Atlassian Cloud through Forge
- Export only what you need for reporting
- Use Jira project permissions to control who can view or edit decisions
Recommended admin checklist
- Review app scopes during installation
- Confirm project permission model for decision visibility
- Define category naming standards for consistent reporting
- Set a recurring export cadence for governance needs