Approval rules
Approval rules decide who can approve, edit or dismiss a card. Nothing is written to your tools until someone with permission says yes.
01
Policies
Every workspace has a default policy. Choose the one that matches how your team works.
anyoneAny member can approve any card. Fastest.
assigneeThe owner of the ticket, issue or PR, or a lead. Recommended.
leadsOnly leads and admins can approve. Members can comment.
02
Per-project overrides
On Team and Enterprise, set a different policy for a Jira project, Linear team or GitHub repository. Overrides always win over the workspace default.
03
Set rules with the API
Manage policies as code by calling the rules endpoint from your infrastructure scripts.
PUT /v1/rules/{project}
{
"project": "jira:TP",
"policy": "assignee",
"fallback": "leads"
}04
Expired cards
Cards that nobody acts on expire after 72 hours and are recorded in the audit log as dismissed.
NoteAdmins can change the expiry window under Settings → Approvals.
Was this page helpful? · Updated Oct 2, 2026