Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

...

For a space administrator setting up a source space who does not have the necessary permissions in a selected target space

In the source space dashboard, on choosing the target space

...

The view and edit permission is needed

...

...

Info

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

The user cannot publish a page

...

  • 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

Error - user with ONLY VIEW permission in target space

...

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

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

    • the published page title is 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

  • is no longer synced for publishing and the publishing status on this page does not change if the source space page is updated

Excerpt
nameuserpermissiontargetspace_solution_duplicatepages

Remove any publishing conflicts 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.

...

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

...

  • 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 Errors publishing to a target space page with page restrictions for details on how to resolve the publishing conflict.

...