Data Access Control Reference

Managers and administrators who can review others need to be limited as to which organizations they have visibility into; this limit controls the level of visibility relative to the user's assigned organization structure.

Visibility is typically enforced by limiting the available organizations that may be selected when running a report or review function.

Select the Highest Organization Level Visible for the system role:

• Root is the top level. All organizations in the LMS are under the Root level. If you select Root, the role can see users in all organizations.
• Select User Org Level (Exclusive) to enable the role to see users in all sub-organizations below their own organization level.
• Select User Org Level (Inclusive) to enable the role to see users in their own organization level and all sub-organizations below it.
• Select a specific level as the highest level of visibility to enable to the role to see users in that level and all organization levels below it.

For more information, see About Organization Visibility Levels.

Select the format used to display Courses in the Manage Center and learner pages where course names are shown:

• Title
• Title (ID)
• (ID) Title

Select Yes to allow users with the role to view and delete the import logs or error logs of CSV files uploaded by other users via the User Data Loader. It also allows users with the role to delete homework files if the Allow Global Homework Files Access permission is also set to Yes.

Select Yes to allow users with the role to delete courses.

Select Yes to allow users with the role to review questions (they can change a question's status to Under Review or Reviewed).

Select Yes to allow users with the role to review questions. They can change a question's status to:

• Under Review
• Reviewed
• Approved
• Retired

Select Yes to allow users with the role to change a question's status back to Work in Progress in order to reopen the question for editing.

Select Yes to allow users with the role to grade exams. They can change the score that a user has originally achieved for answering a question. This also requires the user to have unrestricted access to review the Exam (Exam Editor > Reviewer Permissions) and the Exam Pool. 

Select Yes to allow users with the role to override the question approval workflow and directly set a Work in Progress question to Approved.

Select Yes to allow users with the role to approve or deny enrollment and withdrawal approval requests (in addition to the original approver) for any user within their organizational view.

This can be very useful for training center administrators who need to monitor all enrollments and withdrawals. By default, an administrator or manager is only allowed to act on approvals routed to them directly.

Select Yes to allow users with the role to view the recent activities of users that belong to the role's learning group, and have access to their profile summaries. The role will also have access to the profile summaries of instructors in the same group (in Instructor Info).

Select Yes to allow users with the role to see all participants of a course, instead of just those in the user's organizational view.

This overrides the usual user visibility in the Report Wizard for the following report types:

• Courseware Information
• Exam Results
• Learning Program Detail
• Withdrawn User Details

Select Yes to allow users with the role to print certificates from the Review Participants screen before session ends.

Privilege levels specify the relative hierarchy among different user roles, with 0 being the lowest setting and 9 being the highest, except for system administrators who have a privilege level setting of 10 by default. These numbers are themselves arbitrary within the LMS, and are only meaningful in relation to each other. 

Privilege levels work in conjunction with other access rights. For example, a user can create users only with privilege levels lower than their own. They can update the role of other users whose privilege level is lower than theirs. This prevents local administrators who have access to the User Editor from updating their role (or the role of someone who reports to them) to gain new system privileges that they should not have.