In order to grant a user permissions to publish in Sitecore, they need to be part of the Sitecore Client Publishing role. Once a user is a member of this role, the publishing buttons become visible to the user within the content editor ribbon as well as the main menu. The consequence of this is that it grants the user permission to publish everything via a site publish and in larger applications this can prevent other users from publishing for hours with no easy way to cancel the publish job.
Out of the box Sitecore provides a couple of options around this:
- Remove read permissions to the 'Publish site' option for the role. To do this, edit the read permission
on the core database item /sitecore/content/Applications/Content Editor/Menues/Publish/Publish Site.
- Issue: A user could still initiate a publish from the /sitecore root item and include all sub-items, effectively performing a site publish.
- Configure a publishing scheduled task to perform an periodic incremental publish picking up all new changes.
- Issue: If workflow isn't enabled on all items you can end up with things published that are incomplete.
A potential solution around this is to hide the publishing buttons on items which the context user doesn't have permissions to write to, therefore only allowing them to publish sections of the tree that they can author. For areas of the tree where they only have read access, the publishing button will be hidden. To achieve this, you can follow these steps:
- Create a new class that inherits the Sitecore default command and add logic to the QueryState method to check for write access, for example:
- Patch in the new command referenced in step 1 to replace the default Sitecore command:
Once your solution recompiled, create a new user which is a member of the Sitecore Client Publishing role and then viewing different content items should see the button appearing for items the user can write to and disappearing for items that they cannot.
Tags : Sitecore