Native Confluence Approvals: Setup, Automation & Governance

The Death of the "Please Review" Comment: Confluence Approvals Are Finally Native

If you've spent any time managing an Atlassian Cloud environment, you know the pain of document lifecycle governance. For years, teams have relied on messy @mentions, inline comments, or disconnected Jira Service Management (JSM) tickets just to get a simple sign-off on a Confluence page. It creates a fractured audit trail, frustrates ITSM leads, and leaves you guessing what is actually an approved source of truth.

That changes now. Atlassian is currently rolling out native Confluence Approvals in Open Beta for Confluence Premium and Enterprise tiers.

In most client environments I see, teams end up buying heavy third-party marketplace apps just to stop unapproved runbooks from being published. By bringing this capability native—and tying it directly to Atlassian Automation—Confluence is finally offering a streamlined way to enforce ITSM governance without the bloat.

Who This Is For (and Who It’s Not)

This is for: Atlassian Admins, ITSM Leads, and compliance managers using Confluence Premium or Enterprise who need an explicit sign-off trail for policies, runbooks, or launch plans directly on the page. This is not for: Teams on Confluence Standard (currently excluded from the beta), or organizations requiring highly complex, multi-stage compliance matrices that still demand dedicated Document Management systems.

What You’ll Learn / Outcomes

By the end of this guide, you will know:

• How to activate and configure the new native Confluence Approvals feature.
• How to use publish controls to block unauthorized edits.
• How to integrate the document lifecycle with Atlassian Automation.
• The architectural trade-offs and scaling limitations Atlassian docs won't explicitly highlight.

---

Prerequisites / Setup

To access the beta, you must be on Confluence Premium or Enterprise in Atlassian Cloud. The rollout is gradual, so if you don't see it immediately, you may need to check your "New Features" configuration or open a support ticket to get your instance whitelisted.

To turn it on:

1. Navigate to Space Settings.
2. Look for Status and approvals (or under Configuration > New features).
3. Toggle the Enable Approvals switch.

Add screenshot here showing the Space Settings > Status and approvals toggle enabled.

Once enabled, you’ll notice a new status drop-down at the top of your Confluence pages, allowing users to select "Start an approval" and define their reviewers.

---

Step-by-Step Implementation: Configuring Approvals

The power of this feature isn't just in the approval button—it's in the guardrails you can build around it.

1. Ad-Hoc vs. Enforced Approvers

By default, the page author can select who needs to approve the document. However, for strict ITSM governance, you want Enforced Approvers. In your Space Settings, you can mandate that all approvals must go through a specific group (e.g., infosec-reviewers or engineering-leads). This ensures compliance standards are met without relying on the author to remember who to tag.

2. Implementing Publish Controls (The Real Value)

A status label is just a label unless it enforces a behavior. Confluence now gives you the option to block publishing until required approvals are complete.

When a user requests a review in edit mode (draft version), the draft is essentially locked until the review is resolved. If an older, approved version of the page is currently published, it stays live. This ensures your support agents in Jira Service Management are only ever looking at the approved runbook, protecting your deflection rates and shielding agent capacity from being derailed by inaccurate, unapproved procedures.

Add screenshot here showing the "Block publishing" configuration setting in the Space admin panel.

---

Automating the Lifecycle with Atlassian Automation

Because this is a native feature, Approvals are deeply integrated with Atlassian Automation. This is where you transform a manual sign-off into a hands-free engine.

Expiring Content Example

I usually recommend starting with an expiration workflow to ensure content stays fresh and compliance isn't compromised by stale data.

1. Trigger: Scheduled (e.g., every 6 months) OR Page Approval Expired.
2. Condition: Page has specific label (e.g., compliance-policy).
3. Action: Send a Slack/Teams notification to the page owner AND auto-create a Jira task requesting a documentation review.

You can also use approvals as a Trigger. For instance, when a page status changes to "Approved," an automation rule can dynamically publish a notification to an engineering Slack channel or transition an associated Jira Epic to "In Progress".

Add screenshot here showing a Confluence Automation rule utilizing the "Page Approved" trigger.

---

The Consultant’s Lens: Governance, Trade-offs & Pitfalls

As an Atlassian architect, my job isn't just to tell you how to turn a feature on, but whether you should, and where it breaks at scale. Here are the trade-offs Atlassian documentation doesn’t cover in depth.

Why Implementations Fail

In one enterprise rollout for a global financial client, I've seen resolution rates plateau because process documentation was trapped in endless review cycles. The root cause? Individual users were set as hardcoded approvers. When those individuals went on PTO or left the company, the whole publishing system ground to a halt. The Fix: Always use Atlassian groups or dynamic routing for enforced approvals, never individual named users.

The Missing Piece: True Multi-Stage Approvals

Currently, native Confluence Approvals handle single-stage reviews brilliantly. However, if your business process dictates that a page must first be reviewed by a technical lead, and then routed to Legal, this native feature won't automatically cascade those stages for you. You will still have to rely on manual transitions or complex automation rules to swap out the enforced approvers sequentially. If you need complex routing, an app like Comala Document Management might still be required.

Draft Editing Behavior

Be careful with how users edit pages pending review. If a page is pending review in "View Mode" (the published version) and an author edits the draft and hits publish, it cancels the pending review. You need to explicitly train your teams on this behavior, otherwise, you will see a spike in "ghosted" approval requests and confused managers.

---

Best Practices for Enterprise Rollouts

1. Test in Sandbox First: Don't flip this on globally. Enable it in your Atlassian Cloud Sandbox, apply it to a single IT or HR space, and observe the publishing friction before rolling it out company-wide.
2. Standardize Page Properties: Combine approvals with Page Properties macros. While you can't natively restrict publishing by label or property yet, funneling approved pages into a Page Properties Report gives leadership a single, dynamic dashboard of "Approved Policies."
3. Translate Tech to Business Outcomes: When pitching this to your stakeholders, don't just talk about "page statuses." Frame it around risk: “By utilizing publish blocking, we eliminate the risk of Tier 1 agents executing deprecated SQL commands from unapproved runbooks, directly protecting our SLA and reducing risk.”

---

Conclusion & Next Steps

The native Confluence Approvals Beta is a massive leap forward for Atlassian Cloud governance. It reduces the dependency on third-party apps for basic sign-offs and finally integrates document validation into the core Atlassian Automation engine. While it lacks multi-stage complexity out of the box, it hits the sweet spot for 80% of ITSM and project management needs.

Need help designing your document governance strategy? Don't let your knowledge base turn into a liability. If you're struggling with ITSM documentation processes, compliance auditing, or scaling Atlassian automation across Jira and Confluence, let's talk. I offer deep-dive architectural reviews and advisory services tailored to complex enterprise environments.

👉 Contact me for expert Atlassian consulting.

Subscribe for more Atlassian automation ideas and real-world tips and strategies.