# Integration with Publishing

**Capable Approval** and **Capable Publishing** work hand-in-hand to automate, streamline, and safeguard your content workflow in Confluence—from first draft to final delivery.

With this integration, you can ensure that only **reviewed and approved** content is ever published—whether it’s for internal teams, public documentation, or customer support portals.

## [#](#from-draft-to-delivery-the-integrated-flow)🚦 From Draft to Delivery: The Integrated Flow

Here’s how the integrated workflow operates:

1. **Draft Content in a Private Space**  
Teams create and revise documentation in a private or restricted space (e.g., "Knowledge Drafts" or "Help Center Drafts").
2. **Trigger Approval Automatically or Manually**

  * When enabled, **automatic approval** requests are sent the moment a page is created or edited.
  * Alternatively, reviewers can be added manually per page for more control.
3. **Approvers Review the Page**

  * Assigned reviewers are notified via **Slack** or **email**.
  * They review the content and either approve or reject the page.
  * Approval thresholds (e.g., 2 approvals needed, 1 rejection to fail) must be met.
4. **Publish on Approval**

  * If **auto-publish** is enabled, the page is **automatically pushed** to the designated publishing space once approval is successful.
  * If **auto-publish is disabled**, publishing becomes a **manual step**, giving teams more oversight.
5. **Track Status & Audit Trails**

  * Published pages include a full approval history.
  * Status indicators (Pending, Approved, Published, Outdated) appear at the top of each page.
  * Failed attempts or desyncs are flagged for attention.

## [#](#how-to-set-it-up)⚙️ How to Set It Up

### [#](#step-by-step-approval-publishing-workflow)Step-by-Step: Approval + Publishing Workflow

1. **Enable Capable Approval** Go to: `Space Settings → Integrations → Capable → Approval`

  * Toggle **Automatic Approvals** ON
  * Add **Default Approvers**
  * Set **Minimum Approvers / Rejections**
  * (Optional) Enable **Approval Expiry**
2. **Enable Capable Publishing** Go to: `Space Settings → Integrations → Capable → Publishing`

  * Select the **target publishing space**
  * Toggle **Publish on Approval** ON to automate publishing post-approval
  * Configure **versioning**, **visibility**, or **notifications** as needed

## [#](#what-s-logged-on-a-published-page)🧾 What’s Logged on a Published Page?

Every approved and published page includes:

| **Item**              | **Details**                                               |
| --------------------- | --------------------------------------------------------- |
| **✅ Approval Status** | Approved / Rejected / Expired                             |
| **👤 Approver(s)**    | Names of team members who signed off                      |
| **🕓 Timestamp**      | Date and time of approval and publication                 |
| **📜 Audit Trail**    | Full history of actions for compliance and accountability |

This is essential for regulated environments and large teams managing a high volume of content.

## [#](#real-world-scenarios)🧠 Real-World Scenarios

### [#](#internal-sops)🔐 Internal SOPs

Automatically review and publish IT runbooks only after compliance and security reviews.

### [#](#public-help-centers)📚 Public Help Centers

Draft, approve, and publish to Scroll Viewport or Refined Wiki with full control and traceability.

### [#](#kcs-workflows)🧩 KCS Workflows

Support agents create content → auto-approval triggers → content goes live once verified.

### [#](#marketing-rollouts)🚀 Marketing Rollouts

Route blogs or landing page copy through brand/legal → publish once approved to a public-facing space.

## [#](#benefits-of-the-integrated-workflow)✅ Benefits of the Integrated Workflow

| **Benefit**         | **Description**                                          |
| ------------------- | -------------------------------------------------------- |
| **🎯 Accuracy**     | Only reviewed content gets published                     |
| **🛡️ Compliance**  | Ensure audits are simple and policies are followed       |
| **🔁 Automation**   | Reduce manual steps in content delivery                  |
| **📈 Scalability**  | Easily manage large teams and growing documentation sets |
| **🔍 Transparency** | Know who approved what, and when                         |

## [#](#summary)✨ Summary

When Capable Approval and Capable Publishing are combined, your team gets:

* **Automated reviews**
* **Controlled publishing**
* **Reliable documentation workflows**
* **Traceability and accountability**

No more copy-paste. No missed reviews. Just a **smart, secure, and scalable** publishing system