Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2
minLevel2
absoluteUrltrue
excludeRelated Links
typeflat
separatorpipe

Confluence user permissions to configure publishing

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 can

...

Overview

Space administrator permissions are required in the source and target space to configure publishing.

Confluence view and edit permissions in the source space and the target space are required to publish and sync a page. These permissions are required when

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)

    • adding the target space

    • publishing the space

...

  • manage the publishing configuration settings for an existing source space

    • enable or disable publishing

    • add or change the target space

    • enable or disable single page publishing

    • enable or disable copying of page content properties when publishing

...

  • use the publishing dashboard ellipsis menu to 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 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 confirms they do have enough permissions in the target space

  • the Next option is disabledunavailable and greyed out

...

If the space administrator is changing the target space in an existing source space linked for publishing and does not have the necessary permissions in the new target space

  • 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

Refresh 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. Page-level view or edit restrictions for the publishing user also affect publishing.The view and edit permission is needed

You 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

...

...

Info

The Publish space option is also available in the publishing report.

The user cannot publish a page

Pages with view and edit restrictions for the user are not displayed in the publishing report:

Table of Contents
minLevel3
maxLevel3
outlinefalse
stylenone
typelist
printabletrue

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 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 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

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 byline is not displayed

  • there is no access to the publishing popup

  • the user cannot publish the page using single-page publishing

  • state byline

  • can open the 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
minLevel4
maxLevel4
outlinefalse
stylenone
typelist
printabletrue

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
namepublishing_permissions_example_noeditintarget

If the user publishing the page has view and edit permission on the source space but

  • only view permission on the target space

    • an error message is displayed when trying to publish a page

cpc_error_message_couldnotcopypage.png

no permissions on the target space

In some cases, the page

may

can be published as a new page in the target space without an error

, and the

published

page

title is

name can be appended with a number in brackets

cpc_projectteams_page_name_displayed_with_brackets_sidebar.png

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

  • a duplicate target space is created and synced Project Teams (2)

Screenshot 2024-07-26 at 17.55.21.png

To see both pages in the target space, the user must have at least view permission for each page.

  • subsequent publishing actions sync to this new page

The previously published page in the target space displays the last publishing

status

state byline before

creation of

the publishing conflict occurred and a View source link in the publishing popup

is no longer

. However, it is not synced for publishing

and the publishing status on this page does not change if the source space page is updated

.

One of the target space pages must be removed to prevent publishing conflicts:

  • if the original <Pagename> is removed, a subsequent publishing action removes the appended number brackets on the alternate <Pagename>(2) page

Publishing conflicts and errors can be generated 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.

Excerpt
nameuserpermissiontargetspace_solution_duplicatepages

Remove any publishing conflicts You can resolve the publishing conflict by deleting one of the linked target space pages.

For example:

  • delete the original target space page

  • publish and sync the source page again

The target space page name is updated, and the appended (2) is removed.

Note

If the publishing user has view and edit permission for the Project Teams page and the Project Teams (2) page, the source page cannot be published, and an unexpected error message is displayed.

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 the ability to publish a page.

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

The unpublished page is not reported

The view and edit permissions cause the page to be hidden from the Comala Publishing action for the user who is the space administrator.

For details view the space publishing page

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.

For example:

  • publishing to a target space page with an edit restriction for the publishing user

    • the publishing action identifies the target page exists

    • edit restriction prevents publishing

    • displays an error message

  • 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

    • creates a new page alternate target space page with same name but appended with a number in brackets

      • a user in the target space with view permission sees both the original published page <Pagename> and the newly published page <Pagename>(2)

    • subsequent publishing syncs to the new page <Pagename>(2)

      • publishing by a user with no target space restrictions for the page causes a publishing error

      • removal of the page restrictions without removing the alternate page causes a publishing conflict

    • one of the target space pages must be removed to prevent publishing conflicts

      • if the original <Pagename> is removed, a subsequent publishing action removes the appended number brackets on the alternate <Pagename>(2) page

See https://appfire.atlassian.net/wiki/spaces/CPCL/pages/edit-v2/614694991#Error---user-without-permission-on-an-existing-target-space-page for details and how to resolve the See Errors publishing to a target space page with page restrictions for details on how to resolve this publishing conflict.