Hide menu Last updated: Jul 09 2014

Introduction

In EPiServer CMS 6 it was possible to define how the dashboard would be loaded for a new user through configuration. In EPiServer CMS 7 you can plug in your components directly through the component plug-in functionality. However, currently it is not possible to set up different dashboards for different roles.

Disabling and securing gadgets

Gadgets can be configured to be disabled or to only be available for specific roles. The gadget is specified by its definition name, which normally is the full class name of the type. To disable a gadget, set allowedRoles to “none”. To require specific role access, specify which roles are allowed to use the gadget as a comma separated string. The gadgets will not be available for the user to add. The system will also remove any existing gadgets in a view that the user does not currently have access to.

Example:

XML
<episerver.shell>
    <viewManager>
        <securedComponents>
            <add definitionName="EPiServer.Cms.Shell.UI.Controllers.QuickLinksController" allowedRoles="Administrators" />
            <add definitionName="EPiServer.Shell.UI.Controllers.VisitorGroupsStatisticsController" allowedRoles="None" />
        </securedComponents>
    </viewManager>
</episerver.shell>

Using Shell modules

Views and client resources in OnlineCenter need a virtual path where they can be found. For this reason they are organized into modules. EPiServer CMS is shipped with two modules. The first, a module called Shell, contains the dashboard and resources shared between multiple products. The second CMS contains resources specific to the CMS.

Modules are further organized into protected and public. Public and protected modules are essentially the same except for the root path below which they are expected to be found. The root path for protected modules is configured by a location block to only allow authenticated editors.

Comments