Prevent pages from being published

Adding the capable_never_publish label to a Confluence page prevents that page from being published by Publishing for Capable.

This label provides a safeguard mechanism to ensure sensitive, incomplete, or restricted content cannot be accidentally or inadvertently published to your public or target publishing spaces.

#Purpose and Use Cases

The capable_never_publish label is designed to protect pages that should remain in draft status permanently. Common use cases include:

  • Sensitive Information - Pages containing confidential data, internal discussions, or privileged information that should never be shared publicly

  • Work-in-Progress Content - Drafts, brainstorms, or incomplete documentation that are not ready for publication

  • Archived or Deprecated Pages - Legacy content that should be retained for reference but never published

  • Internal Process Documents - Operational procedures, meeting notes, or team-specific guidance meant only for internal consumption

  • Testing and Experimentation - Sandbox pages used for testing publishing workflows or content structures

#How It Works

When the capable_never_publish label is applied to a page:

  1. Publishing is blocked - The page cannot be published through the Publishing for Capable interface, regardless of user permissions or approval status

  2. No automatic publishing - Even if approval workflows are configured with autopublishing enabled, pages with this label will not automatically publish

  3. Manual override protection - Users cannot manually publish the page through the standard publishing action

  4. Label persists - The restriction remains in effect as long as the label is present on the page

#How to Apply the Label

  1. Open the page you want to protect

  2. Click the Details icon in the bottom-right floating action bar

  3. In the Labels section, select +

  4. Type capable_never_publish

  5. Press Enter or select Add

  6. The label takes effect immediately