Confluence page restrictions
There is nothing to set up. Because restrictions matter for compliance, here is exactly what happens.
#How
To read and republish restricted pages, the app adds its own app user, with read and update access, to the restrictions on source pages. It adds itself back whenever someone edits the restrictions on a page in a space with publishing enabled.
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 working | 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.
