Sitecore - Standard Roles for Users

Question

I create users for a practical project and came up with three authors, reviewers, and publishers.

author - should be able to create, edit and delete items.
reviewer - should be able to read and approve subjects.
publisher - should be able to read all subjects and publish those that have been approved.

I read in the article that these roles will be sufficient for the content author - Archiving Sitecore clients and Sitecore Client users , and therefore it is assigned to the author.

When you log in as the author, the insertion option is grayed out !!!!. So, I logged in again as an administrator and tried to provide access to the Home element (read, write, etc.) for the author, but he says that access is denied.

Please clarify for me the following:
1. Are the users I was thinking about right or working well in a real scenario?
2. Why can’t I give the author access to the Home element. 3. Does it create a custom role. Should there be a standard role (s) for these users that are common to each project. 4. Please propose roles that I should assign to my author, reviewer, and publisher

Answer 1

This question is not suitable for SO recommendations, but to answer your questions:

• It’s unusual to have a specialized publisher. More common is that the workflow is automatically published after the approval of the content that I would expect. You will probably only succeed in 2 roles.

• These roles should be sufficient, but check doco, please check to see if your admin user receives an access denied message or your author. Administrator users need not deny anything; your security setting is probably causing the problem (permissions, not roles).

• The standard roles are detailed so that you can customize your setup. There are several examples of sites you can get (for example, launchsitecore.net) that can show you how to use these roles, as well as the documentation. You can also post to community.sitecore.net

• There is a combination of roles and privileges needed to achieve this too detailed for SO. Refer to documentation, various blogs, or a sample site to learn how to use security features in the real world.

Answer 2

You can set it using the Workflow function and changing security rights at the workflow level. The simplest workflow structure should be:

Initial step 1

• Send command (moves the item to step 2)

Pending Approval 2

• Approve command (moves item to step 3)
• Reject command (moves the item to step 1)

Pending Publishing Step 3

• Publish command (moves item to step 4)
• Reject command (moves items to step 2)

Final Step 4 published

• Automatic public action (the standard action that will publish an item automatically as soon as the item appears in its final state)

All 3 roles must be members of at least Sitecore\Author . It provides basic access to element editing features. Remember to explicitly allow Write, etc. Access using the Security Editor . If for some reason it doesn’t work on checking current rights using the Access Viewer application, as soon as you select a specific account and security element, you can check the allowed and forbidden rights with explanations on the right side.

Then you need to set access at the workflow level (for example, the reviewer can execute the Approve and Reject commands in the Pending Approval state, as well as in other states. The same is for the author and publisher).

Useful documents (valid for Sitecore 8.x): https://sdn.sitecore.net/Reference/Sitecore%207/Security%20Reference.aspx https://sdn.sitecore.net/Reference/Sitecore%207/Workflow% 20Reference.aspx