HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubNuGetDev CommunitySubmit a ticketLog In

Configure the dashboard

Describes how to configure the dashboard and gadget availability in Optimizely Content Management System (CMS) versions 10 and 11.

πŸ“˜

Note

This legacy content applies to Optimizely Content Management System (CMS) versions 10 and 11.

You can plug in your components directly through the component plug-in functionality. However, you cannot set up different dashboards for different roles.

Disable and secure gadgets

You can configure gadgets to be disabled or only available for specific roles. The definition name specifies the gadget, 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 any existing gadgets from a view the user cannot access.

Example:

<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>

Use Shell modules

Views and client resources in the Online Center need a virtual path where you can find them, so they are organized into modules. CMS ships with the following modules:

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

CMS further organizes modules protected and public modules that are essentially the same except for the root path below, where you expect to find them. CMS configures the root path for protected modules by a location block to only allow authenticated editors.