Content reviews are a crucial part of most workflows.

Often called "Approvals", they are characterized by a decision to Approve or Reject the content, and based on that decision, the workflow will generally transition to another state.

Defining reviews

One or more reviews can be added to a state using the {approval} macro:

      {approval:Technical Review|assignable=true}

The approved and rejected parameters on the {state} macro determine which states to transition to if the review is Approved or Rejected


By default, a user must have Edit or Admin permissions in order to take part in a content review.

However, if the App configuration is set to allow anyone to view Workflow Activity and Drafts then users with View permission, so long as they are logged in to Confluence, will be able to take part in reviews (since version 4.6).


The people who make the decision to Approve or Reject are called reviewers.

The settings of the {approval} macro determine

  • if anyone can review
  • who can review
  • who must undertake the review (and is pre-assigned by the workflow on transition into the content review state)
  • if users are allowed to assign reviewers
  • and if the review is assignable you can limit who can be assigned

All assigned reviewers must reach the same decision (all be in agreement) before the review will be considered approved or rejected.

You can use Events to change this behavior, for example, to facilitate fast-tracked rejections.

Anyone can review

You can set the approval so that Anyone (with edit and view permission) can undertake the review.

A single reviewer decision will action the approved or rejected transition.


Assignable review

The approval can be set to allow one or more users to be assigned to the review.

Once a user is assigned, only that user can undertake the review. But additional users can be assigned if the transition has not taken place.

If more than one user has been assigned, all users must agree for a transition to occur.

Users who have not yet undertaken a decision can be unassigned.


Minimum reviewers

You can set a minimum number of reviewers to agree on the approved decision for the transition to occur.

A minimum can be required when the approval is set so

  • anyone can approve
  • the content review is assignable
  • reviewers are limited

Limiting who can be assigned

You can also limit who can be assigned.


Limiting reviewers

You can also simply limit users who can review. Only these users will be able to undertake the review.

None of the users' avatars who can undertake the review are displayed in the workflow popup.


All other users will simply see the Approved and Rejected options disabled (greyed out) in the workflow popup.

Requiring users to undertake a review

Reviewers can be mandated to undertake a review. On transition into the content review state, the user avatar will be appended to the workflow popup.

All reviewers must agree for a transition to occur.


(info) If the workflow reviewers are changed whilst in a state with assigned reviewers, the changes will only take effect for the content review on the next transition into that content review state.

Multi-group reviews

In cases where more than one team of reviewers is required, rather than adding the teams to a single approval, just add more {approval} macros to the state and use a different approval for each team.

All the separate approvals must be undertaken and agreed in order for the approval transition (approved or rejected) to take place. Until the transition takes place any reviewer can amend their approved or rejected decision.

The approvals can be completed in any order. But you can use conditions to set the order in which the approvals in a state are undertaken.

See: Workflow Authoring Guide - Example - Adding Multiple Reviews

(info) Using multiple approvals in a single state is a process decision for you. You may simply wish to have a separate state for each approval.


Reviewers can optionally be required to verify their credentials before making a review.

Each approval can be edited to require credentials for the reviewers. Global administrators can set the method of authentication.

See: Reviewer AuthenticationCredentials prompt, E-Signatures, E-Signatures Configuration - Global


By default, assignees and page watchers will receive notifications about the review progress, and all interactions will be tracked in the Activity Report - Content.

Approval role 

Use the optional approval role feature to record the roles that your approvers are performing. This is a more flexible method of capturing roles compared to named reviews and allows you to easily assign ad hoc roles when necessary. 

When creating a workflow using workflow builder, to use approval roles, open the advanced section of 'Edit approval' and tick 'Enable roles'

Roles can also be enabled in the {approval} macro by including the roles=true  parameter.

Clear History will remove any added approval roles. Note this will also remove all workflow history.



All aspects of the review process generate Events, which can be used to Trigger Actions.

Reviewer assignment events:

  • pageapprovalassigned
  • newsapprovalassigned
  • approvalunassigned

Approval events:

  • pageapproved
  • newsapproved
  • pagerejected
  • newsrejected

App configuration

Workflow Activity and Drafts Visibility

Who can see the workflow and draft content?

If set to Everyone, then View-only users can also participate in the review.

Page Update Reset ApprovalDuring an active review, if the content is updated should existing approvals be reset?
Approval CommentShould comments be mandatory when participating in a content review?
Approval – AssigneeShould assigned reviewers receive email notifications about the content review?
.approval.minquerySet how many characters must be typed when searching for reviewers


See also

Workflow Authoring Guide:

User Guide:

Reporting Guide: