Skip to content
English
Customer portal
Go to fldata.com
  • There are no suggestions because the search field is empty.

Permissions

Permissions enable select users to have additional access (e.g., administration, settings, or reporting) to the MOC module in Frontline.

About MOC Permissions

Permissions for the MOC module are classified into two categories: Module Permissions and Organizational (Company, Division, and Account) Permissions.

Below are the guidelines for MOC permissions

User accounts without additional permissions can complete the following from their Frontline Desktop under the appropriate tabs:

  • Create MOCs through predefined MOC pre-approval shortcut(s).
  • Complete any assigned MOC task (Evalution, collaboration, approval, etc.).
  • Track MOCs they are role players on.
  • Sign-off on MOC Send Notice notifications.

MOC Module Permissions

The MOC Module Permissions alone will not provide users with any additional access than a user account without permissions. Module Permissions need to be paired with Organizational Permissions and vice versa.

  • MOC User: This is the lowest level of the MOC module permissions and should be reserved for users needing limited access to MOC In Process, Completed, and Voided folders per organizational unit (as low as account level). This allows users to control various aspects of their in-process events/action items as originators or team leaders.
  • MOC Power User: This is a higher level of the MOC module permissions and should be reserved for advanced users responsible for the overall MOC administration in a division or company. This permission grants all access given by MOC User permissions and full access to elements in MOC > Settings. It also allows users to update or change any originator's MOCs. 
  • MOC Super User:  This is the highest level of the MOC module permissions and should be reserved for very few administrative users who need the ability to make significant organizational changes to an MOC. This permission grants the user additional functionality to make significant MOC changes from creation to completion. 
    • Example: Make changes to MOC details post-approval stage, reassign & delete inbox requirements, etc.

The super user permission does not allow you to remove mandatory requirements. 

  • MOC Personal Agent:  Does not grant access to the MOC module menu. A MOC Personal Agent can complete a desktop-assigned MOC task on behalf of another person. This permission allows an MOC role player to create a personal agent to complete all their MOC desktop tasks in their absence.  MOC Personal Agent permission can be granted to anyone with a basic user account and with or without the consent of the MOC User or MOC Power User.

MOC Organizational Permissions

The Organization Level Permissions must be used together to provide users with the appropriate level of access. 

  • MOC Admin: Granted at organization (company, division, or account) level for MOC Module access MOC > Events, MOC > Action Items. This permission is automatically granted at the division level when permission is given to the MOC User or MOC Power User.
  • MOC Report: Granted at organization (company, division, or account) level for MOC Module access to MOC > Reports. This permission is automatically granted at the division level when permission is given to the MOC User or MOC Power User.

Upon granting MOC User or MOC Power User permissions, the system automatically grants MOC Admin and MOC Report permissions for the user's default division. Below is a list and description of each.

MOC Permission Setup

Below are examples how the two types of permissions work together to provide certain access within the MOC module. 

  • MOC User:
    • MOC User (module permission) + MOC Admin Access (Organization permission at company, division or account level).
      • Grants access to the MOC In Process, Completed and voided folders
      • Allows them to create new MOCs from the In Process folder
      • For MOCs they are the Originator or Implementation Manager - Change the MOC details, assignees, manage tasks on behalf of other people, void and resubmit their MOCs. 
    • MOC User (module permission) + MOC Report Access (Organization permission at company, division or account level).
      • Grants access to the Reports menu
  • MOC Power User:
    • MOC Power User (module permission) + MOC Admin Access (Organization permission at company, division or account level).
      • Grants access to the MOC In Process, Completed and voided folders
      • Allows them to create new MOCs from the In Process folder
      • For all MOC's - change the MOC details, assignees, manage tasks on behalf of other people, void and resubmit their MOCs. 
      • Access to configure all elements in the MOC Settings menu.
    • MOC Power User (module permission) + MOC Report Access (Organization permission at company, division or account level).
      • Grants access to the Reports menu
  • MOC Super User:
    • MOC Super User (module permission) + MOC Admin Access (Organization permission at company, division or account level).
      • Grants access to the MOC In Process, Completed and voided folders
      • For all MOC's - change the MOC details, assignees, manage tasks on behalf of other people, void and resubmit their MOCs. 
      • Reassign Approvers while the task is in inbox status (on the approvers desktop)
      • Delete Approvers during the Approval stage
      • Delete any MOC task at any point
      • Reorder any MOC task at any point
    • MOC Super User (module permission) + MOC Report Access (Organization permission at company, division or account level).
      • Grants access to the Reports menu
  • MOC Personal Agent:
    • MOC Personal Agent (module permission)
      • Does not need to be combined with organizational permissions
      • Allows users to create a personal agent from their desktop which allows other users to complete their MOC tasks in their absence. 

Manage MOC Permissions

The instructions below provide detailed steps on how to grant and delete / inactivate MOC permission for a user. All permissions are maintained through the LMS module, and a user must have LMS Admin permission at the company or division level to grant, update, or delete/inactivate a user's permissions.

How to manage MOC Module Permissions

By default all users are granted LEARNER, ViewCompanyLibraries and ViewPublicLibraries.
  1. Navigate to People > People Information in the LMS module.
  2. Find and select the user requiring additional permissions.
  3. Select the Permissions tab.
    1. The existing permissions granted to the selected user will appear in a list on the left side of the screen with the Permission Details form on the right side of the screen.
  4. To add a permission, select New on the toolbar. Then select the checkbox next to the permission that is to be granted to the user.
  5. To delete a permission, select the permission. Then select Delete on the toolbar. 
    1. A pop-up dialog box will appear asking for confirmation that the selected permission is to be deleted. Select ok in the pop-up dialog confirmation box to delete the permission.
  6. Select Save on the toolbar.

All permissions are automatically granted to the user's default division. To grant permissions at different organization levels, navigate to the Company, Division, or Account tabs.

How to manage MOC Organization Level Permissions

  1. Navigate to the organization level tab that the MOC permission needs to be granted at (Company, Division, or Account tabs) for the selected person.
    1. If there are more than one of these items, there will be only one set as the default under the default column.
  2. From the list of accounts, divisions, or companies displayed, select the name of the organizational level to grant access to for the selected user.
  3. To add a permission, select MOC Admin and/or MOC Report checkboxes.
  4. To delete a permission, deselect MOC Admin and/or MOC Report checkboxes.
  5. Select Update on the toolbar to update the organization level with the changes made.
    1. The selected organizational permissions will be updated from "No" (unchecked) to "Yes" (checked) accordingly.