I want to create a new user with 'Settings' permissions, but to allow access only to Dictionary and to hide access to everything else(Docyment Type,Stylesheets and etc.).
Could you explain in further detail how the user rights are managed for a custom section?
Because if it's possible to set user permissions for custom sections out of the box this is indeed the workaround since it's unfortunately not possible to limit acces to folders in the different sections at the moment.
FYI, we tried kows's idea, but only users with 'settings' access can view the dictionary item editor. There seems to be some sort of hard-coded requirement.
If an 'editor' logs in (without settings access), the custom tree throws an 'access denied' error. Only way to get past this seems to be allowing them access to 'settings' which defeats the purpose.
Allow access only to 'Dictionary' in 'Settings'
Hi,
I want to create a new user with 'Settings' permissions, but to allow access only to Dictionary and to hide access to everything else(Docyment Type,Stylesheets and etc.).
Can I do it?
Thanks,
kukuwka
what i would try is make a new custom section and try to add dictionary in there, setting the rights for that section.
Hi kows
Could you explain in further detail how the user rights are managed for a custom section?
Because if it's possible to set user permissions for custom sections out of the box this is indeed the workaround since it's unfortunately not possible to limit acces to folders in the different sections at the moment.
/Jan
if you go to a user the bottom options allow you to set which sections a user may see,
if you add a custom section it appears between those
Hi kows,
How can I add a custom section ?
Thanks,
kukuwka
Hi kukuwa
I think this blogpost is a good starting point. It covers what you need to know I think http://www.geckonewmedia.com/blog/2009/8/3/how-to-create-a-custom-section-in-umbraco-4
/Jan
Thanks :)
Comment author was deleted
FYI, we tried kows's idea, but only users with 'settings' access can view the dictionary item editor. There seems to be some sort of hard-coded requirement.
If an 'editor' logs in (without settings access), the custom tree throws an 'access denied' error. Only way to get past this seems to be allowing them access to 'settings' which defeats the purpose.
is working on a reply...