...
manage the publishing configuration for an existing source space
...
use the ellipsis menu option Clear Publishing configuration
...
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 User permissions for publishing 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.
...
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 dialog box on the page
the user cannot publish the page using single-page publishing
...
When the target space page has a page-level edit restriction, in the source space, a user with edit permission on the source space page:
can view the publishing status state byline
can open the publishing dialog box
...
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.
...
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.
...
By default, for a new space publishing configuration, the The Comala Publishing for Confluence Cloud app add-on user permissions in the target space are used for publishing actions.
User permissions for publishing are The Select user performing publishing action option is set using a dropdown menu.
...
Comala Publishing for Confluence Cloud app add-on user permissions
user permissions of the User who triggers User responsible for the action
Removing 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.
...
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.
...
| 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. |
...