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

...

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

  • use the publishing setup wizard to Configure Publishing in a space (currently not used 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 Clear Publishing configuration

...

The other publishing configuration options are also disabled.

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.

...

The view and edit permission is needed

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

...

Single page publishing

...

Space publishing

As a space administrator publishing pages using

...

...

The user cannot publish a page

  • if the user does not have edit permission for a source space page

  • if the user has view and edit permission in the source space but does not have these page permissions in the target space

User without edit permission in source space

...

  • 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

User without view or edit permission on a page in the target space

If the published target space page has page-level permissions for the publishing user in the source space, the publishing user can

  • view the publishing status

  • open the workflow popup

  • cannot see the Publish option

...

The View Published Version button is displayed, but no link is available unless you have view permission on the target space page.

Error - user with ONLY VIEW permission in target space

...

  • 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, with the page may be published as a new page in the target space without an error

and the

published

page

title is

name 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 byline before creation of the publishing conflict and a View source link in the publishing popup

but is no

longer

loner 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

Excerpt
nameuserpermissiontargetspace_solution_duplicatepages

Remove any publishing conflicts The publishing conflict is resolved 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.

...

Without edit permission for a page in the source space

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

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.

...

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 and an error messageis 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).

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

...

A publishing conflict and error is generated if:

  • 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

    causes a publishing conflict

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 the this publishing conflict.

Publishing app add-on user

Permissions for the Comala Publishing app user

The Comala Publishing app user is added to all spaces by default, with the following permissions:

...

Do not change the permissions for the app user!