At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Draft term | Select Submit for Review | Review-pending version | Submission is not approval |
| Permitted reviewer | Select Approve or reject | Recorded review decision | Creator, editor, or submitter cannot approve the same content |
| Approval reason | Save it with the decision | Explainable approval evidence | A reason does not replace policy authority |
| Later content change | Create a new version | New review cycle | Prior approval does not cover changed content |
How it works
- A term manager creates or edits the draft.
- The manager selects Submit for Review.
- A different permitted reviewer opens the term.
- The reviewer checks the meaning and usage guidance.
- The reviewer records a reason and selects Approve or reject.
- Any later content change returns through review.
Example
An author updates the definition of “critical supplier.” That author submits the version but cannot approve it. A second term manager reviews the change and records the decision. The approved version keeps both actors and the reason.
What this does not mean
Four-eyes approval separates term-content duties. It does not approve Confluence pages, controlled documents, releases, or electronic signatures. Organizations still define reviewer qualifications and authority.
Related questions
Next step
Assign at least two qualified term managers before requiring four-eyes approval.
View on Atlassian Marketplace