4 results found
-
Better access rights management for assets
There is a lack of functionality around limiting access to assets for different user groups. Any user group with editor access will currently have access to all blocks and media. A user group with access to a part of the pagetree shouldn't have access to all the assets.
6 votes -
Granular Access Rights for CMS Settings Area
In the Settings area anyone with the "CMSAdmin" or "Content Admins" has access to the full rights to edit anything in here.
We should be able to set granular rights to these function areas for example if I want a specific user group to be able to make updates to Content Types but not Manage Website and Access Right this should be possible2 votes -
Granular Permissions for CMS Admin Tools
We have a client that wants to only give users only access to certain tools in the CMS/Admin area, IE the ability to Import/Export.
To the best of my knowledge this permission is specified in the EPiServer.CMS.Admin.UI module and is set to episerver:cmsadmin.
I've attempted to override settings using our own instance of AdminModule, but haven't had any luck. I know I can intercept/remove MenuItems, but I believe I will be unable to prevent users from actual accessing the content with a URL.
It would be great to be able to set these permissions at a more granular level at…1 vote -
User management on PAAS portal
Having one tab on PAAS portal for Azure Access Users. Only technical contact (TC will be able to see this tab, which having a list of current users who is having access to the customer's resource group because TC will be aware to correct the list, remove/update those who is not working on that project anymore. This is to prevent possible security risk for their environments.
In the case, the technical contact becomes invalid, he/she can submit a button "Request to change technical contact information" on this tab. And a new form will be popped up for him/her to fill…58 votes
- Don't see your idea?