The Four-Eyes Principle in Jira: Approval Workflows for Independent Review
The four-eyes principle, also known as dual control, maker-checker, or the two-person rule, is a control mechanism that requires one person to initiate an action and another independent person to review and approve it before it takes effect. German banking supervision uses the term Vier-Augen-Prinzip, for example in BaFin's MaRisk. Related controls appear in other frameworks, such as the segregation of duties control in ISO/IEC 27001:2022 (Annex A 5.3) and the internal controls over financial reporting that SOX Section 404 requires companies to assess.
No single individual should have unchecked authority over a critical action. One person initiates (the "maker"), and a separate person verifies and approves (the "checker"). The separation reduces the risk of errors, fraud, and non-compliance, because a second independent reviewer catches what the first person missed or wouldn't flag on their own. In Jira, that usually means the person who raised or worked on an issue should not approve it, and an audit trail shows who approved and when.
Define the Rule for Your Process
Teams in automotive, aerospace, finance, healthcare, and pharma may use independent review as part of their controls. The required reviewer independence, approval count, and evidence depend on the activity and the applicable requirements. Match the approval workflow to your organization's policy and the evidence it needs.
Write down who initiates the work, who implements it, and who may approve it. A maker and a checker are two people, but this does not automatically require two additional approvers or reviewers from different departments.
Use Native Jira Approvals Where They Fit
Jira Cloud or Jira Data Center? The native features below are for Jira Cloud. Jira Software Data Center does not include native approval steps. Jira Service Management Data Center does have approvals for service requests. Group Sign-Off is available on both Jira Cloud and Jira Data Center.
Native Jira Cloud approval steps support multiple reviewers and configured field-based exclusions. Atlassian's approval setup guide covers excluding users identified by Reporter, Assignee, or another user field. Availability depends on your plan and project type.
JSM records who participated and when they approved or declined in its Approvals activity view. An ordinary workflow transition and a native approval step are different controls. Use the native step when its reviewer rules meet your policy.
Group Sign-Off adds separate group thresholds at the same gate. Exclusions must be configured per approval field using the 4-eyes principle option. The app does not automatically identify or exclude the author. See how to prevent self-approval in Jira for the field mapping and configuration.
Native Jira vs. Group Sign-Off
| Feature | Native Jira / JSM Cloud | Group Sign-Off |
|---|---|---|
| Multiple reviewers | Native approval steps | Configurable group rules |
| Reporter and Assignee exclusions | Configure in the approval step | Configure per field using 4-eyes principle |
| Decision records | Native approval activity | App decision history |
| Different group thresholds at a gate | JSM requires the same count from each group | Separate threshold per group |
| Workflow gate | Native approval step | Configured Group Sign-Off condition |
Set Up a Four-Eyes Approval Workflow with Group Sign-Off
Group Sign-Off adds formal multi-person approval workflows to Jira. The following steps configure independent review.
1. Create Segregated Approval Groups
Define the required reviewers and exclusions for each critical transition:
- Exclude conflicting roles: configure the user fields identifying the requester and implementer. Follow the self-approval guide.
- Choose reviewer groups: include Engineering and QA separately when your policy requires both perspectives.
- Set approval counts: decide how many approvals each group needs and check that exclusions leave enough eligible reviewers.

2. Attach Approvals to Workflow Transitions
Add a Group Sign-Off condition to the critical transitions (e.g., "Ready for Release", "Deploy to Production") and require the configured approval result. Check other transitions and any separate release or deployment actions for paths around that gate.
3. Keep Decision Evidence
Group Sign-Off records approvals, rejections, and delegations with the acting user and timestamp. Keep the applicable configuration alongside that history. Review settings for revised votes, administrator decision removal, and approval resets when planning retention.

4. Configure Delegation
Define who can receive a delegated approval and how the team will monitor pending decisions when an approver is unavailable.
Evidence for a Control Review
When auditors ask "how do you enforce dual approval?", you need to show:
- Policy: documented rules for who can approve what
- Enforcement: technical controls that prevent bypassing, not guidelines alone
- Evidence: timestamped records of every approval decision
- Segregation: proof that the author and approver are different people
Group Sign-Off can support the configured gate, reviewer rules, and decision records. Your team must connect them to the policy, check bypass paths, and preserve the evidence needed for its review.
Common Implementation Mistakes
- Unnecessary approvers: additional reviewers can create delays. Choose counts based on the decision and your policy.
- Conflicting responsibilities: different people can still hold conflicting roles. Define the independence required. Being on the same team does not by itself invalidate a review.
- Approval fatigue: if everything requires sign-off, people rubber-stamp. Reserve formal approvals for critical transitions.
- No rejection path: approvers need a structured way to reject with comments, not just approve or ignore.
- No visibility into approval status: teams should be able to see at a glance which approvals are pending, complete, or overdue. Using RAG status indicators to track approval workflow health can surface bottlenecks before they delay releases.
From Manual to Automated
A configured gate can block a transition until the required reviewers approve. Recording decisions alongside the work reduces manual record keeping, while the team still needs to monitor pending approvals and preserve evidence.
The other shift is from sequential to parallel. Instead of an approval request waiting in one inbox before it moves to the next, multiple groups can review at the same time. In a manual process, those handoffs are usually where the waiting happens. Configured exclusions help prevent self-approval when the role fields accurately identify the people doing the work.
Key Takeaways
- The four-eyes principle separates the maker from the checker. Set additional reviewer counts according to your policy.
- Native Jira Cloud approval steps support multiple reviewers, configured exclusions, and decision records.
- Group Sign-Off adds separate group thresholds and configurable workflow conditions. Configure its exclusions explicitly.
- Moving from manual approvals to tool-enforced ones keeps pending decisions visible on the issue and lets groups review in parallel instead of one after another.
- Start with critical transitions only. Over-applying approvals leads to rubber-stamping and approval fatigue.
Getting Started
If your team needs to enforce the four-eyes principle in Jira, start with a free trial of Group Sign-Off on the Atlassian Marketplace. It's available for Jira Cloud and Jira Data Center.
Visit the Group Sign-Off product page for a full feature overview, or read our step-by-step guide on how to set up approval workflows in Jira.