Overview
With same-space publishing, each piece of content (page or blog post) can have concurrent draft and approved versions.
Activating same-space publishing
To use same-space publishing, just add the final=true parameter to one of the {state} macros in your workflow – this marks it as the final Published state.
{workflow:name=In-space Publishing}
{state:Editing|submit=Review}
{state}
{state:Review|approved=Published|rejected=Editing}
{approval:Review|assignable=true}
{state}
{state:Published|final=true|updated=Editing}
{state}
{workflow}
Subsequent drafts
The updated parameter can be applied to published states to ensure that any subsequent edits are pushed to a draft state.
In the example markup above, editing the Published state content will result in the new version being in the Editing state.
State colours
By default, draft (unpublished) states will have an 
orange circle and published (final=true) state will have a 
green circle.
For more information, see Status Indicator Circles.
Note: Since v5.0.8, colours can be customised on state-by-state basis via the colour parameter on the {state} macro.
Permissions
If a workflow has a published (final=true) state, then all other states in that workflow will be considered draft (unpublished) states.
Editing – draft
Review – draft
Published – published
By default, users who only have View content permission can only see the most recently published version of each page or blog post. If they try to view draft (unpublished) versions, they will see an error like this:
Users with Edit and Admin permissions can see all versions of content, and can switch between the latest draft and published versions via the Workflow Status Bar.
Not for secure publishing
Note that same space publishing is for when you want to direct users to the correct version of the content. It is not a secure publishing option to hide draft content. While view only users might default to seeing the approved content the most up to date content is still visible through the page history or search index. If you require that draft updates are not visible to some users we recommend using Different-space publishing where Confluence permissions can hide the draft space entirely.
Notifications
The {set-message} macro can differentiate between draft and published versions of content.
PDF and Word export
When exporting content as PDF or Word using native Confluence features, either as individual pages or an entire space, the distinction between Published vs. Draft content will be respected.
For more information, see: Confluence PDF and Word Export.
App configuration
| Setting | Where | Notes |
|---|---|---|
| Workflow Activity and Drafts Visibility | Determines which users can access the workflow information and tools on a page. If using same space publishing the users not in this group will see the approved version of the content by default. | |
| Default View | Determines whether Published content is seen by default. | |
| Published View Macro Transform | Determines whether {include} and {excerpt-include} macros display most recently Published version or, regardless of workflow state, the latest version of content. |
