In the source space publishing dashboard, a space administrator can select the user permissions in the target space that are used for single-page publishing and space publishing actions:
Comala Publishing for Confluence Cloud app add-on user permissions
user permissions of the User responsible for the action
By default, for a new space publishing configuration, the Comala Publishing for Confluence Cloud app add-on user permissions in the target space are used for publishing actions.
The choice of user permissions for publishing is set using the Select user performing publishing action dropdown.
Pages are published using the selected user’s permissions in the target space.
When publishing is configured to use the app add-on user, only the app add-on user requires edit permission in the target space.
There is no need for a Confluence user who publishes content (a page editor or a space administrator) to have edit permissions in the target space.
Removing user edit permissions in the target space can support compliance with published documents. |
On installation of Comala Publishing, the app add-on user is automatically added with edit permission in all the spaces on the Confluence site.
Using the app add-on user permissions to publish pages can support compliance, as a user undertaking a single page or space publishing action does not require edit permission in the target space.
If the app add-on user permissions are not selected, the publishing user must have the required permissions in the target space.
The app user permissions are used when publishing occurs using an applied Comala workflow, irrespective of the selected publishing configuration for User publishing permissions.
The app user permissions are used when publishing occurs using an applied Comala workflow, irrespective of the selected publishing configuration for User publishing permissions.
When the Select user performing publishing action option is set as Comala Publishing for Confluence Cloud, the add-on user is recorded in the target space page history.
Initial publish and sync of a page
If the page has not been previously published, publishing and syncing add the app add-on user as the page's owner and creator in the target space.
The Confluence target space page history displays the Comala Publishing for Confluence Cloud app add-on user in the Changed By entry.
Publish and sync a page after the initial publish using the user permissions
If the page has been previously published using the publishing user permissions, the app-add-on user is added as the user who last changed the page in the target space.
The Confluence target space page history displays the Comala Publishing app add-on user in the Changed By entry each time the page is published and synced. The latest Changed By entry also displays the user who initially published the page and is the page creator.
When using a Comala workflow to publish a page and the app add-on user permissions are used for publishing, the add-on user is added to the Changed By entry in the target space page history.
When using a Comala workflow to publish a page and the app add-on user permissions are used for publishing, the add-on user is added to the Changed By entry in the target space page history.
When the Select user performing publishing action option is set as the app add-on user:
the space publishing report displays the Confluence user as the Publisher of the last whole space publish action
the publishing report for the target space displays
Last updated by as the Comala Publishing for Confluence Cloud app add-on user
Last synced by as the Confluence user who triggered the publishing action
In the source space, the Last updated by and Last synced by values are the Confluence user who triggered the publishing action. |
In the page analysis diagnostic tool, when the Select user performing publishing action option is set as the app add-on user:
the Publisher in the page manifest is the Confluence user who triggered the publishing action
in the publishing configuration, the Publish as add-on user is
YES - space publishing action uses the app add-on user permissions
When the Publish as add-on user value is NO, the space publishing action uses the current Confluence user permissions for publishing. |
The exportable Manifest screen includes a true value for addonUser in the source manifest and isPublishedAsAddon in the space configuration.
If the Confluence user permissions are used, the values are set as false.
When the app add-on user permissions are used for the publish action on a page with page-level restrictions, the Comala app user must have permission to view and edit the page.
A warning message is displayed for a page that cannot be published due to page-level restrictions or space permissions.
A warning message is displayed for a page that cannot be published due to page-level restrictions or space permissions.