| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Space administrator permissions are required in the source and target space to configure publishing.
Confluence view and edit permissions
...
To configure publishing from a source space to a target space, a user must have
space administrator permission in the source space
space administrator permission in the target space
Source space set up
In a space settings publishing dashboard, a space administrator canin the source space and the target space are required to publish and sync a page. These permissions are required when
publishing a single page as a page editor
publishing all the pages in a space as a space administrator
Adding a page restriction to a page in the source space or a page in the target space affects its ability to be published by anyone not included in the restriction.
Publishing in a space can be configured to use the Comala Publishing app add-on user permissions in the target space instead of the publishing user’s permissions. This allows pages to be published without needing specific user permissions in the target space.
Confluence permissions to configure publishing
Space administrator permission is required in the source and target space to set up and configure publishing.
Source space
In the publishing dashboard of the selected source space, a space administrator can:
use the publishing setup wizard to Configure Publishing in a space (currently not used space must not currently be in use as a source or target space)
...
manage the publishing configuration settings for an existing source space
...
use the ellipsis menu option . Clear Publishing configuration
...
...
publish all the pages in the space using Publish space
For a
...
space publishing action, the space administrator requires view and edit permission for all the pages in the source space and the target space. Page-level restrictions that do not include the space administrator may affect the ability to publish the page. The Select user performing publishing action option can be set to use the app add-on user permissions in the target space when publishing instead of the space administrator user permissions.
Target space
Setting up linked spaces for publishing requires space administrator permission in the target space as well as the source space.
In the source space dashboard, on choosing the target space
...
when a space administrator chooses a target space where they do not have the necessary administrator permissions
a warning message confirming you confirms they do not have enough permissions in the target space
the Next option is unavailable and greyed out
...
selected target space is greyed out
a warning message is displayed confirming the user does not have enough permissions in the target space
...
The If you select a target space where you don’t have space administrator permissions, all other publishing configuration options are also disabledgreyed out and inactive.
| Info |
|---|
When the permissions warning is displayed, you can refresh the dashboard to return the source space publishing configuration to the existing target space. |
Confluence user permissions for publishing
A user publishing a page from the source space to a the target space requires view and edit permission in both spaces. The view and edit permission is neededPage-level view or edit restrictions for the publishing user also affect publishing.
You also need at least the following space permissions in the target space to publish a page:
View All
Add and Delete Pages
Add and Delete Attachments
...
...
| Info |
|---|
If you want to restrict your users from editing pages in the target space, publishing can be configured to use the Comala Publishing add-on user target space permissions. |
View and edit permissions are required
as a page editor publishing a single page using the publishing popup dialog box on a page
...
...
as a space administrator, publishing all the pages
...
whole space publishing Publish space the space settings publishing dashboard
the Publish pages option in the space using space publishing
Pages with view and edit restrictions for the user are not displayed in the publishing report:
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
User without edit permission
...
on a source space page
If a user only has view permission for a page in the source space
the publishing status state byline is not displayed
there is no access to the publishing popupdialog box on the page
the user cannot publish the page using single-page publishing
When a space administrator does not have edit permission on a source space page, the page is not included in a space publishing action
The unpublished page is not reported or included in the list of 'Pages not published' in the whole space publishing report.
User without
...
edit permission on a published page in the target space
If When the published target space page has a page-level permissions for the publishing user edit restriction, in the source space, the publishera user with edit permission on the source space page:
can view the publishing statusstate byline
can open the workflow popup
cannot see the Publish option
...
publishing dialog box
...
However,
they cannot publish the page - the Publish button for single-page publishing (if enabled in the space) is not displayed
the page is not included in a space publishing action by a space administrator when they do not have edit permission on the target space page.
| Info |
|---|
The View Published Version button is displayed in the publishing dialog box on the page, but |
...
the link is |
...
unavailable unless you have view permission on the target space page. |
As a space administrator, you can configure the User Permissions for Publishing setting in the source space to use the Comala Publishing for Confluence add-on user’s permissions in the target space. This allows pages to be published without needing specific user permissions in the target space. This setup is helpful for compliance needs, as it prevents users from editing published pages in the target space.
Publishing using the app add-on user permissions in the target space
Publishing in a space can be configured to use the Comala Publishing app add-on user permissions in the target space instead of the publishing user’s permissions. For new spaces, the app-add-on user is selected by default in the Select user performing publishing action setting.
...
This allows pages to be published without needing specific user permissions in the target space. The Comala Publishing for Confluence Cloud app add-on user permissions in the target space are used for publishing actions.
The Select user performing publishing action option is set using a dropdown menu.
...
Comala Publishing for Confluence Cloud app add-on user
User responsible for the action
Using the app add-on user for publishing lets you remove user edit permissions in the target space and can support compliance with published documents.
The Comala Publishing app add-on user is added to all the spaces in the Confluence Cloud site by default with the following permissions:
...
You should not change the space permissions for the app user! The app add-on user permissions are used, for example, when publishing using an applied Comala workflow.
Publishing permission conflicts and errors
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Error - user with ONLY VIEW permission in target space
A user is unable to publish a new page in the source space if they have
view and edit permission in the source space
but only view permission in the configured target space
...
Error - user without view or edit permission in target space
A user is unable to publish a new page in the source space if they have
view and edit permission in the source space
but no page permissions in the configured target space
...
Error - when permissions change on an existing published page in the target space
If a page has already been published and synced to the target space, subsequent publishing actions are affected if the page-level permissions change and cause a publishing conflict.
| Excerpt | ||
|---|---|---|
| ||
If the user publishing the page has view and edit permission on the source space but
 In some cases, the page can be published as a new page in the target space without an error, and the page name can be appended with a number in brackets  The publishing user does not see the original published page in the target space - they do not have view permission. For example, when publishing a source space page, Project Teams with an existing target space page with added page restrictions that affect the publishing user
 To see both pages in the target space, the user must have at least view permission for each page.
The previously published page in the target space displays the last publishing status state byline before the publishing conflict occurred and a View source link in the publishing popup. However, it is not synced for publishing. One of the target space pages must be removed to prevent publishing conflicts:
Publishing conflicts and errors can be generated when:
You must remove one of these pages to solve this publishing conflict and clean up your target space. |
| Excerpt | ||
|---|---|---|
| ||
You can resolve the publishing conflict by deleting one of the linked target space pages. For example:
The target space page name is updated, and the appended (2) is removed.
|
Space administrator permissions for publishing
The space administrator requires permissions in the source space and the target space to publish and sync pages
space administrator permission
view and edit permission
Adding a page restriction to a page in the source space or a page in the target space affects its ability to be published by anyone not included in the restriction.
Without edit permission for a page in the source space
...
|
If a space administrator does not have page edit permission for a page in the source space
when publishing all the space content, the page is not published
The unpublished page is not reported and not included in the list of 'Pages not published' in the whole space publishing report.
In addition, the Publish option in the publishing popup is not displayed, and the space administrator cannot publish the page using single-page publishing.
Without required permissions in the target space
Page-level permissions on the target space page
When publishing and syncing existing published pages, the space administrator must have view and edit permission on the target space pages.
A space administrator cannot publish and sync a source space page to a target space page with an edit or view restriction for the publishing user.
publishing to a target space page with an edit restriction for the publishing user
edit restriction prevents publishing, and an error is displayed
publishing to a target space page with a view and edit restriction for the publishing user
restrictions prevent publishing action syncing to the existing page
However, publishing creates a new alternate target space page with the same name but appended with a number in brackets.
...
subsequent publishing syncs to the new page <Pagename>(2)
If you view the target space with only view permission, you can see both the original published page <Pagename> and the newly published page <Pagename>(2).
You can generate publishing conflicts and errors when:
someone with no page restrictions for the original target space page publishes the source space page
removal of the page restrictions without removing the alternate page
You must remove one of these pages to solve this publishing conflict and clean up your target space.
If the original <Pagename> is removed, a subsequent publishing action removes the appended number brackets on the alternate <Pagename>(2) page.
See Errors publishing to a target space page with page restrictions for details on how to resolve this publishing conflict.
Publishing app add-on user
A Comala Publishing app user is added to all spaces in the Confluence Cloud site.
Permissions for the Comala Publishing app user
The Comala Publishing app user is added to all spaces by default with the following permissions:
...