# Integration with Capable Approval 📝 Capable Publishing and Capable Approval are designed to work seamlessly together, giving your team a structured, traceable, and flexible way to manage how content goes from draft to published. **Publish only what’s been reviewed - and know who approved it, when, and why** With this integration, you can ensure **every page that’s published has gone through the proper review process**, without manual handoffs or disconnected workflows. --- ## [#](#how-it-works)How It Works Once approval is configured in your space, the approval system becomes part of the publishing workflow: 1. **A page is created or updated** in a draft space. 2. Capable automatically (or manually) triggers an **approval request**. 3. Assigned approvers receive notifications via **Slack or email**. 4. Once the approval meets the defined criteria (e.g., 2 of 3 approvals), the page is: * Automatically published to the target space **if auto-publish is enabled**, or * Available for manual publishing if you prefer more control. 5. The published page includes an audit of who approved it and when. ![Integration with Capable Approval for Confluence](https://help.gocapable.com/images/984be3e4-dc9e-453d-8743-e536980eeca1.webp) --- ## [#](#setup-overview)Setup Overview To connect approvals with publishing: 1. Go to **Space Settings → Capable → Approval Settings**. 2. Enable **Automatic Approvals** (optional). 3. Add **Default Approvers** for the space. 4. Set your **Minimum Approvers** and **Minimum Rejections** thresholds. 5. (Optional) Set **Approval Expiry** rules. 6. Toggle **Publish on Approval** to auto-publish once approved. --- ## [#](#why-it-matters)Why It Matters Integrating Capable Approval with Publishing ensures your team’s content is: * **Reviewed before it goes live** * **Compliant with internal or external guidelines** * **Traceable** with a full audit trail * **Free of copy-paste or manual errors** * **Scalable** for teams managing many contributors and approvers Whether you're running a help center, SOP library, or public product docs, this keeps your publishing process tight, reliable, and stress-free. --- ## [#](#approvals-are-logged-on-published-pages)Approvals Are Logged on Published Pages Every published page includes: * The **approval status** * The **approver(s)** who signed off * The **timestamp** of when it was published This makes audits easy, and gives stakeholders confidence in the quality and accuracy of published documentation. ![Confluence Publishing Byline Panel](https://help.gocapable.com/images/f8f78810-5681-4d78-b4c8-d2719a76bcf4.webp) --- ## [#](#flexible-for-all-teams)Flexible for All Teams * Product teams can set up fast approvals from PMs or designers. * IT teams can enforce multi-level reviews from security and compliance. * Marketing teams can route content through brand and legal before pushing live. Set different rules per space to meet each team’s needs. ![Confluence Approval Settings](https://help.gocapable.com/images/e667b88a-3f00-4bbf-8371-78e0a889fdcd.webp) --- ## [#](#summary)Summary With Capable Approval integrated into Capable Publishing, you can: * Automate reviews for every page update * Control what gets published (and when) * Keep a clean approval trail for every published doc * Scale your content process without sacrificing quality > **Pro Tip**: Combine multi-stage publishing with space-level approval settings for even more control - like legal reviews before marketing launches or compliance checks for IT policy updates.