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