The Module Definition Manager module is used to configure and manage permissions for the available module definition types available to construct content.

This module functions outside the realm of the normal permissions hierarchy. It can be viewed only by a user with membership in Site Administrators site-level roles with no regard to permissions assigned to the tab on which the module is placed. For more information on the roles referenced in this section please see the role based security topic. Administrative users can configure additional module settings by clicking the button.

This module presents a sortable data grid that allows you to view and maintain module definitions, view usage statistics, and manage usage permissions.

Adding New Module Definitions

To add a new module definition members of the Site Administrators role click the button which will open the module definition editor and allow an administrative user to define the details of the new module definition.

Editing Existing Module Definitions

To edit an existing module definition members of the Site Administrators role click the button which will open the module definition editor and allow an administrative user to define the details of a new module definition. From within this editor the View Usage button is available which will detail the location of every instance of the module definition in the system and allow the user to navigate to the site of a specific module instance.

Module Definition Attributes

The following attributes are exposed through the editor:

•Module Definition: This is name of the module definition. It may not be blank and must be unique within the system. By convention administrative module definitions should end in (Admin)

•Controller Type Name: This is the fully qualified type name of the MVC controller class that renders the module.

•Help Source URL: (Obsolete) This is the application relative path to the HTML help file for the module as rendered in legacy editions of the portal.

•16x16 Icon URL: This icon will appear in those module skins that include icons in the header.

•Options: The array of check box options that dictate how the module behaves and where it can be placed.

Managing Module Definition Permissions

Clicking the permissions editor button will display the user interface for assigning role access to the module definition. If a module is placed on a tab but the end-user is not in a role that has been assigned at least Use permission the module will not render for that user. Permissions for module definitions include None, Use, and Full Control. The Use permission allows end-users to interact with the module on tabs for which they have at least read permissions. The Full Control permission allows end-users to place the module and configure it on tabs for which they have authoring permissions. Most common modules are assigned Use permissions to members of Anonymous Users and Full permissions to Authenticated Users and Site Administrators. Administrative modules typically have Full permissions to Site Administrators and sometimes additional permissions assigned to Security Administrators and Dashboard Managers.

Send comments on this topic.

Created with an evaluation copy of HelpSmith.
To remove this notice, you should purchase the full version of the product.