I have a user that we dont want to give admin access to, but still want some of the functionallity from it. The indexing section to where you can boost values, rules and include in search is all greyed out with the priviledges they have know. Could someone point me to what role or security setting they need. Thank you.
Can the user edit other fields on that item?– Dean OBrienFeb 13 at 17:15
Access right applies on the item level, It will make the whole item editable or disabled. Access right does not work on the section level.
It looks like the current user you are logged in with does not have proper access writes to edit the item. You need to identify a role that is blocking the current user from read/write items. You need to use Access Viewer to review user/roles access rights and update roles according to to allow write access.
- Go to launchpad and click on
- Select role/user from the top left
Roles and Usersselection box.
- Select an item that is not accessible for the user/role.
- It would come up with a right-side pane to show access permission specifically to the selected role/user.
In most cases
sitecore\Author role is enough to allow content editing.
Hope it helps!
I have added the permissions to this item in the above screenshots and as you can see this person has all the privileges to edit this item. Feb 10 at 14:59
Could you check field write access as well? byteium.com/2019/05/… Feb 10 at 15:51
Ok just checked those to show and they are empty, they dont have a checkbox available for it though either. I checked a user with admin rights and its empty there as well. Feb 10 at 16:18
Have you used any custom roles? A few more things to try 1) You can also check if there is any explicit break inheritance applied or any field level security applied (sitecoretricks.wordpress.com/2017/12/31/… . 2) You can remove applied roles one by one to investigate which roles causing the issue, then review the applied access right for the specific role and make it work. Feb 11 at 3:56
Ok thanks for the help, not sure what is blocking it or allowing it. Seems like only admin role allows it so will just go a different route. Thanks. Feb 14 at 18:11