Hide menu Last updated: Sep 21 2015

In Episerver CMS 6, you could define how to load the dashboard for a new user through configuration. From Episerver CMS 7, you can plug in your components directly through the component plug-in functionality. However, you cannot set up different dashboards for different roles.

Disabling and securing gadgets

You can configure gadgets 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 are not available for the user to add. The system also removes from a view any existing gadgets that the user does not 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, so they are organized into modules. Episerver CMS ships with the following modules:

  • Shell. Contains the dashboard and resources shared between multiple products.
  • CMS. Contains resources specific to the CMS.

Modules are further organized into protected and public modules that 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