Permissions
Armada inherits Jira’s permission model. Users can only perform actions they’re already authorized for in Jira.
Required Permissions
Section titled “Required Permissions”For Campaign Creators
Section titled “For Campaign Creators”| Permission | Scope | Purpose |
|---|---|---|
| Browse Projects | Target projects | View and select projects |
| Create Issues | Target projects | Create child issues |
| Link Issues | Parent project | Create issue links |
For Campaign Viewers
Section titled “For Campaign Viewers”| Permission | Scope | Purpose |
|---|---|---|
| Browse Projects | All involved projects | View campaign status |
For Approvers
Section titled “For Approvers”| Permission | Scope | Purpose |
|---|---|---|
| Browse Projects | Site-wide | Review pending launches |
| Designated as approver | Armada config | Approve/reject launches |
Permission Checks
Section titled “Permission Checks”Armada validates permissions:
- Before launch: Checks write access to target projects
- On recall: Checks delete/transition permissions
- On nudge: Checks comment permissions
Troubleshooting
Section titled “Troubleshooting””Permission denied” errors
Section titled “”Permission denied” errors”- Verify your Jira permissions in the target project
- Ask your Jira admin to grant necessary permissions
- Use Fleet Health Check to validate access
Cross-project campaigns
Section titled “Cross-project campaigns”You need permissions in both:
- The parent issue’s project
- Each target team’s project