Confluence page restrictions
Nothing to configure. This is compliance-relevant and should be described explicitly in customer-facing docs.
#How
The app adds its own app user (read and update) to the restrictions of source pages so it can read and re-publish restricted content, and re-adds itself whenever restrictions are edited on a page in a publish-enabled space. Restrictions are NOT copied to the published page.
#Where you do it
Task | Where |
|---|---|
Publish a chosen set of pages by their current state | Capable Publishing space page → Pages → Published / Unpublished / Outdated / Moved / Failed / Invalid lists |
Recover publishing when its background jobs stop worki | Confluence settings → Capable → Publishing tab |
Hide Publishing from the whole site or from one space | Confluence settings → Capable → Capabilities tab (Visible/Hidden), or Space settings → Capable → Capabilities (Auto/Always/Never) |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Enable publishing | Space settings → Publishing → Setup tab | - |
Target space | Space settings → Publishing → Setup tab | - |
Allow manual publishing | Space settings → Publishing → Setup tab | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Allowed publishers list | 50 users maximum; individual users only, | - |
"Publish all pages" / Full Sync | Reads at most 1000 items in a single que | - |
Bulk selection from the space page lists | Capped at 1000 items per run | - |
#Related
Better with company.
