Skip to content

ApprovalFlow release notes — March 2026

ApprovalFlow now supports coordinated reviews across groups of related pages and programmatic approval workflows through a 3LO REST API.

  • Group related page changes: Create a named Change Set with a shared title, summary, and optional external reference URL.
  • Version-aware rollup state: See the overall state as open, in_review, partially_approved, all_approved, has_rejections, or stale.
  • Per-page version tracking: Compare the current version, approved version, stale state, and version difference for every page.
  • Bulk submit: Submit all eligible pages for approval in one action and receive a success or failure result for each page.
  • Preflight (dry-run): Check whether pages are eligible for submission without changing page data, which supports automated review workflows.
  • Change Set context in comments: Page comments created during submission include the Change Set title, summary, and clickable reference URL.
  • Archive: Mark completed Change Sets as read-only.
  • Nine REST API endpoints: Manage Change Sets and submit individual pages programmatically.
  • 3-legged OAuth (3LO) authentication: Request only the ApprovalFlow scopes needed by an integration.
  • Change Set operations: List, create, update, archive, inspect, submit, and run preflight checks.
  • Page operations: Submit an individual page or run a page-level preflight check.
  • Audit traceability: Customer-visible approval history identifies API actions and records the associated OAuth client.
  • Real user identity: API actions run as the authenticated Atlassian user rather than a shared system identity.
  • Change Sets tab: Review rollup states and open per-page details from the space dashboard.
  • Submission feedback: Change Set results explain why individual pages were skipped.
  • Manage Space tree: Clearer expand and collapse icons are shown only for pages that have children.

This release adds four ApprovalFlow OAuth scopes for REST API clients: Read Change Sets, Manage Change Sets, Read Approval Status, and Submit for Approval.

No action is required for teams that use ApprovalFlow only in Confluence. REST API clients must complete Atlassian 3LO authorization and request the scopes needed for their integration.