Who the published copy is written by
The copy is written into the target space by the app itself, not by the person publishing, so ordinary authors need no permission in the target space at all. Manual publishes are attributed as "Published by <name>", approval publishes as "Published via Approval", and system publishes fall back to the display name "Capable". To be able to read and rewrite restricted source pages the app adds its own app user to the source page's restrictions when a publish runs, and re-adds itself whenever restrictions are edited on a page in a publish-enabled space.
#Where to find it
Every publish
#Where you do it
Task | Where |
|---|---|
Decide whether people can publish by hand, and whether | Space settings → Publishing → Setup tab |
Choose where published pages land and whether the tree | Space settings → Publishing → Structure tab |
Reuse pages that already exist in the target space ins | Space settings → Publishing → Structure tab |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Enable publishing | Space settings → Publishing → Setup tab | - |
Target space | Space settings → Publishing → Setup tab | - |
Require comment on publish | Space settings → Publishing → Setup tab | - |
#Worth knowing
There is no unpublish or delete action. "Clear state" only breaks the link, changing the target space only clears records, and Reset to default leaves every published page in place. Published copies must be deleted by hand in the target space, and nothing in the product says so.
#Related
How it actually behaves.
