Roles & Permissions

Ariel Mitevski asked on July 20, 2016 09:51

Hello,

I'm trying to add the Localization module for CMS basic users. I noticed that there are a few places in Kentico where I can grant this permission but I did not really understand the purpose of each one.

In the Role application -> CMS Basic User -> UI personalization -> Administration - I can check/uncheck what section/module the role can see in the UI but what I don't really understand is why it does not work for all the modules/sections. If I check or uncheck the "Polls" module for example, It will add/remove the app from the CMS Basic user's UI but it will not work as such for the localization module or the eCommerce section (and many others).
In the Modules application -> Localization - There is also a list where I can set "permission to see 'Localization' UI element" by role/site/action (kinda like in the role application) but no matter what I check or uncheck for the CMS Basic user, it still doesn't appear in the list, It basically has no effect at all.
In the Permissions application - I see a list of module with the permission matrix but unfortunately, the Localization module is not part of the list of modules available.

How can I add the Localization module for a basic user (or any other role for that matter)?

What the difference between those 3 places to set permissions? What the best practice?

...and is there any particular reason why the localization module is not part of the list in the Permissions application?

Sorry if that's a lot of question for one post but I felt they were all related somehow.

All the best,

roles permissions modules

Correct Answer

Jan Hermann answered on July 21, 2016 10:27

There are global applications like Localization that are not accessible by anyone else except the global administrator. We call them global applications and most of them are in Development section of the application list.

If you need them to be available for your editors you need to create custom module and replicate its functionality.

0 votesVote for this answer Unmark Correct answer

Recent Answers

Roman Hutnyk answered on July 20, 2016 14:13

UI Personalization allows you to show/hide particular section of admin interface.

Permission is for security purposes. User might be allowed to see some UI elements, but won't be able to browse it if he has no permission.

So basically you need to configure both.

There are some pages in the admin interface, those are allowed only for administrator or even global admins, e.g. Email Queue. This is implemented in code behind (*.cs file for particular page/control), so you can't change it through Kentico interface.

0 votesVote for this answer Mark as a Correct answer

Ariel Mitevski answered on July 20, 2016 14:35 (last edited on July 20, 2016 14:38)

Is there a list of what can be controlled and what cannot?

It does not seem logic to give the user the option in the Kentico interface if it actually does not do anything (for the localisation case at least since I can't even see the module in the UI - see screenshots attached)

Image Text

0 votesVote for this answer Mark as a Correct answer

Zach Perry answered on July 20, 2016 21:55

You might have to clear the cache after changing the settings to get it to display in the navigation.

0 votesVote for this answer Mark as a Correct answer

Ariel Mitevski answered on July 21, 2016 10:12

Already did it. The odd things is that it works fine with some modules (even without clearing the cache) but doesn't with others such as the Smart Search or the Localization...

0 votesVote for this answer Mark as a Correct answer