ELIS 1.9 Manual

ELIS Permissions/Capabilities

Curriculum Administration Permissions

Curriculum administration permissions


Associate curriculum management items - block/curr_admin:associate

  • This enables curriculum management items to be shared between roles.
  • For roles to associate curriculum management items, each role must have this permission enabled.
  • For example, a curriculum administrator role (with this permission enabled) is assigned to a user in a curriculum, which gives the user access to only courses in the curriculum. A second role is created (with just this permission enabled) and assigned to the user in a course, the user will have access to the course and they could add it to the curriculum.

Create classes - block/curr_admin:class:create

  • This allows a user to create classes.
  • Assign this permission in the system or ELIS contexts.
  • For example, a role with this permission and the "view class" permission is assigned to a user in a curriculum. The user may view any classes that are linked to the curriculum, and they can create a new class from any course in the curriculum.
  • Note: Anytime a role has create, edit, or delete permissions for a curriculum, course, etc., there also needs to be a view permission for that item included with the role.

Delete classes - block/curr_admin:class:delete

  • This allows users to delete classes.
  • Assign this permission in the system or ELIS contexts.
  • For example, a user assigned this permission at the system level, may delete any class in ELIS. A user assigned this role in a curriculum, may delete any class that is an instance of a course in the curriculum.

Edit class - block/curr_admin:class:edit

  • This allows users to edit classes.
  • Assign this permission in the system or ELIS contexts.
  • For example, a user assigned this permission in a curriculum, may edit any class linked to that curriculum.

Manage class enrolments - block/curr_admin:class:enrol

  • This allows a user to manage class enrollments.
  • Assign this permission in the system or ELIS contexts.
  • For example, a user assigned this permission in a class, may only manage enrollments for that class.

Manage cluster users' class enrolments - block/curr_admin:enrol_cluster_user

  • This allows a user to manage class enrollments for users assigned to clusters they manage.
  • Assign this permission to a cluster administrator in the class, track or cluster context.
  • The purpose of this permission is to limit the users cluster administrators may enroll in classes to just users in their clusters. When using a cluster administrator role, we recommend creating a second role for curriculum permissions. For both roles allow the "associate curriculum management items" permission. Then assign the cluster administrator role in clusters and the curriculum administrator role in curricula, tracks, and/or classes.

View Classes - block/curr_admin:class:view

  • This allows users to view classes.
  • Assign this permission in the system or ELIS contexts.
  • This permission is providing view permissions only, and should be used when classes need to be viewed with the role. For example, if a user has "create class" permission, they also need "view class" permission to be able to see the Manage Class link and create classes.

Create clusters - block/curr_admin:cluster:create

  • This allows a user to create clusters.
  • Assign this permission in the system or cluster context.
  • Create a role with this permission and the "view cluster" permission, then assign it to a user in a cluster. The user can view the cluster and can create sub-clusters of the cluster.

Delete Clusters - block/curr_admin:cluster:delete

  • This allows a user to delete clusters.
  • Assign this permission in the system context or cluster context.
  • Create a role with this permission and the "view cluster" permission, and then assign it to a user in a cluster. The user can view and delete the cluster and/or its sub-clusters.

Edit Clusters - block/curr_admin:cluster:edit

  • This permission allows users to edit clusters.
  • Assign this permission at the system or cluster context.
  • For example, a role with this permission and the "view cluster" permission is assigned to a user at the system level, the user may edit any cluster.

Manage cluster membership - block/curr_admin:cluster:enrol

  • This permission allows users to manage cluster membership. This permission doesn't work in ELIS versions 1.9.2 and earlier. It should be fixed for the 1.9.3 release.
  • Assign this permission in the system and cluster contexts.
  • For example, create two roles: (1) allows "manage cluster membership" and "view clusters", and is assigned at cluster level; (2) allows "view users" and is assigned at the system level. On the User tab of the cluster where the user is assigned the first role, the user can add any user on the site to the cluster.

Manage cluster users' sub-cluster membership - block/curr_admin:role_assign_cluster_users

  • This allows a user to manage enrollments in sub-clusters of the cluster they are managing.
  • Assign this permission at the cluster context.
  • For example, assign this permission to a user in a cluster context, and they can assign users of the cluster to sub-clusters of the cluster.

Only assign roles in a cluster to cluster members - block/curr_admin:role_assign_cluster_users

  • This allows a user to assign roles in the cluster/sub-clusters for only members of the cluster.
  • Assign this permission in the clusters/sub-clusters contexts.
  • For example, users assigned to a cluster are added to the Users tab of the cluster. With this permission those users can be assigned roles in the cluster, or sub-clusters of the cluster.
  • For this permission to work the role must also include the permission Assign roles to users - moodle/role:assign. The permission is in the Course section.
  • The main use case for this permission is to allow an organizational cluster administrator to assign roles to users that are assigned to the clusters they manage.

View clusters - block/curr_admin:cluster:view

  • This allows a user to view clusters only.
  • If a role allows other cluster permissions this should be enabled to make clusters visible.

Configure curriculum management settings - block/curr_admin:config

  • This allows a user to view/create/edit cluster classifications. Use this permission with the "manage curriculum curricula" permission for access to the configuration screen.
  • This role should be assigned to ELIS administrators at the system level.
  • Users with this permission can manage the settings in the Curriculum Administration block > Admin > Cluster Classification. The Admin > Configuration screen should be enabled with this permission in a future release. For now use the "manage curriculum curricula" permission for access to the admin configuration screen.

Create course - block/cur_admin:courses:create

  • This allows a user to create courses.
  • Assign this permission in the system context.
  • For example, assign this permission and the "view courses" permission at the system level, and it allows a user to view all the courses on the site and add courses to the site.

Delete courses - block/curr_admin:course:delete

  • This allows a user to delete courses.
  • Assign this permission in the system or ELIS contexts.
  • For example, assign this permission and the "view courses" permission in the system context, and it allows a user to view and delete all the courses on the site. Assign this in a curriculum context, and it allows a user to view and delete courses of the curriculum.

Edit courses - block/curr_admin:course:edit

  • This allows user to edit courses.
  • Assign this permission in the system or ELIS contexts.
  • For example, assign this permission and the "view courses" permission in the curriculum context, and it allows a user to view and edit courses of the curriculum.

View courses - block/curr_admin:course:view

  • This allows a user to view courses.
  • Assign this permission in the system or ELIS contexts.
  • For example, a user assigned the 'create course' permission at the system context will need this permission to see the Manage Courses link and create courses.

Create curricula - block/curr_admin:curriculum:create

  • This allows a user to create curricula.
  • Assign the permission in the system context.
  • For example, assign this permission and the "view curricula" permission at the system context, and it allows a user to view all curricula on the site and create curricula.

Delete curricula - block/curr_admin:curriculum:delete

  • This allows a user to delete curricula.
  • Assign this permission at the system context or ELIS contexts.
  • For example, assign this permission and the "view curricula" permission in a curriculum, and it allows a user to view and delete the curriculum. Assign this at the system level and the the user could view and delete any curriculum on the site.

Edit curricula - block/curr_admin:curriculum:edit

  • This allows a user to edit curricula.
  • Assign this permission in the system or ELIS contexts.
  • For example, assign this permission and the "view curricula" permission in a curriculum, and it allows a user to view and edit the curriculum.

Manage curriculum enrolments - block/curr_admin:curriculum:enrol

  • This allows a user to manage curriculum enrollments.
  • Assign this permission in the system or curriculum contexts.
  • For example, create a role with this permission and "view curricula" permission and assign it to a user in a curriculum. The user can access the curriculum and can manage enrollments for the curriculum.

Manage cluster users' curriculum enrolments - block/curr_admin:curriculum:enrol_cluster_user

  • This allows a user to manage curriculum enrollments for user of clusters they manage.
  • Assign this permission in the cluster context.
  • Testing.

View curricula - block/curr_admin:curriculum:view

  • This allows a user to view curricula.
  • Assign this in the system or ELIS contexts.
  • For example, a role with create, edit, or delete permissions for curricula, will also need view curricula permission.

Create environments - block/cur_admin:environment:create

  • This allows a user to create environments.
  • Assign this permission in the system context.
  • For example, create a role with this permission and the "view environment" permission allowed and assign it to a user at the system level. The user can view/create environments by going to the Progress Reports block > Information Elements > Manage Environments.

Delete environments - block/cur_admin:environment:delete

  • This allows a user to delete environments.
  • Assign this permission in the system context.
  • For example, create a role with this permission and the "view environment" permission allowed and assign it to a user at the system level. The user can view/delete environments by going to the Progress Reports block > Information Elements > Manage Environments.

Edit environments - block/cur_admin:environment:edit

  • This allows user to edit environments.
  • Assign this permission in the system context.
  • For example, create a role with this permission and the "view environment" permission allowed and assign it to a user at the system level. The user can view/edit environments by going to the Progress Reports block > Information Elements > Manage Environments.

View environments - block/cur_admin:environment:view

  • This allows a user to view environments.
  • Assign this permission in the system context.
  • Allow this permission for roles where environments need to be viewed.

Manage Curriculum Curricula - block/curr_admin:managecurricula

  • This allows a user access to most of the items in the Curriculum Administration block.
  • Assign this permission to ELIS administrators at the system level.
  • This permission has the capability to manage all the items in the Curriculum Administration block, except cluster classifications and Data Hub. The name of this permission will be changed in a future release.

Manage Curriculum Files - block/cur_admin:managefiles

  • This allows a user to manage curriculum files.

Receive course due to begin notifications - block/curr_admin:notify_coursedue

  • This allows a user to receive course due to begin notifications.
  • Assign this permission in the system or user contexts.
  • There are also Notification settings that need to be configured in the Curriculum Administration block > Admin > Notifications. There are 3 checkboxes for each notification: user, user with permission at system context, and user with permission at user context. If no checkboxes are selected, then no notifications will be sent regardless of permissions enabled by a role.

Receive course expiration notifications - block/curr_admin:notify_courserecurrence

  • This allows a user to receive course expiration notifications.
  • Assign this permission in the system or user contexts.
  • For example, assign a user this permission in a user context, and they will receive a notification when the user's credit for a course expires.

Receive curriculum completed notifications- block/curr_admin:notify_curriculumcomplete

  • This allows a user to receive curriculum completed notifications.
  • Assign this permission in the system or user contexts.
  • For example, assign a user this permission in the system context, and notifications will be sent for users when they complete a curriculum.

Receive curriculum due to begin notifications - block/curr_admin:notify_curriculumdue

  • This allows a user to receive curriculum due to begin notifications.
  • Assign this permission in the system or user contexts.
  • For example,

Receive curriculum not completed notifications - block/curr_admin:notify_curiculumnotcomplete

  • This allows a user to receive curriculum not completed notifications.
  • Assign this permission in the system or user contexts.
  • For example, assign this permission in a user context, and notifications will be sent when that user has not completed a curriculum.

Receive curriculum expiration notifications - block/curr_admin:notify_curriculumrecurrence

  • This allows a user to receive curriculum expiration notifications.
  • Assign this permission in the system or user contexts.
  • For example, assign this permission in the system context, and notifications will be sent for users on the dates that credit expires for curricula they are enrolled in.

Receive track enrollment notifications - block/curr_admin:notify_trackenrol

  • This allows a user to receive track enrollment notifications.
  • Assign this permission in the system or user contexts.
  • For example, assign this permission to user1 in the user2 context, user1 with the role permission receives notifications when user2 is enrolled in a track.

Note: Class notifications are in a different section of the permissions page. The next page in the docs covers the class notifications permissions.

Can over enroll a class - block/curr_admin:overrideclasslimit

  • This allows a user to over enroll a class.
  • Assign this permission in system or ELIS contexts.
  • For example, enable this permission, the view classes, and the manage class enrollments permissions, then assign that role to a user in a track. The user can see the Manage Class link in the Curriculum Admin block, is able to view the classes of the track, and control enrollments of the classes, including over enrolling classes.

Create Tags - block/curr_admin:tag:create

  • This allows a user to create tags.
  • Assign this permission in the system context.
  • For example, create a role with this permission and the "view tag" permission allowed, and assign it to a user at the system level. The user can view/create tags by going to the Progress Reports block > Information Elements > Manage Tags.

Delete Tags - block/curr_admin:tag:delete

  • This allows a user to delete tags.
  • Assign this permission in the system context.
  • For example, create a role with this permission and the "view tag" permission allowed, and assign it to a user at the system level. The user can view/delete tags by going to the Progress Reports block > Information Elements > Manage Tags.

Edit Tags - block/curr_admin:tag:edit

  • This allows a user to edit tags.
  • Assign this permission in the system context.
  • For example, create a role with this permission and the "view tag" permission allowed, and assign it to a user at the system level. The user can view/edit tags by going to the Progress Reports block > Information Elements > Manage Tags.

View Tags - block/curr_admin:tag:view

  • This allows a user to view tags.
  • Assign this permission in the system context.

Create tracks - block/curr_admin:track:create

  • This allows a user to create tracks.
  • Assign this role in the system or ELIS contexts.
  • For example, if this permission is assigned in the curriculum context, it allows a user to create tracks that are an instance of that curriculum.

Delete tracks - block/curr_admin:track:delete

  • This allows a user to delete tracks.
  • Assign this permission in the system or ELIS contexts.
  • For example, if this permission is allowed in a curriculum context, it enables tracks of that curriculum to be deleted.

Edit tracks - block/curr_admin:track:edit

  • This allows a user to edit tracks.
  • Assign this permission in the system or ELIS contexts.
  • For example, allowing this permission in a track context, would enable editing for that track.

Manage track enrollments - block/curr_admin:track:enrol

  • This allows a user to manage track enrollments.
  • Assign this permission in the system or ELIS contexts.
  • For example, assigning this permission in a track context, allows a user to manage the track enrollments. Assigning this permission in a curriculum context, allows a user to manage track enrollments for all the tracks of the curriculum.

Manage cluster users' track enrollments - block/curr_admin:enrol_cluster_user

  • This allows a user to manage track enrollments for a cluster of users.
  • Assign this permission in the cluster or sub-cluster contexts. Track permissions will be needed somewhere to have a access to tracks to enroll the cluster of users.
  • For example, assigning this permission in the cluster context will provide access to the cluster of users and their enrollment in tracks. Creating a second role with track permissions and assigning that to the user in a track or curriculum, will provide access to tracks to assign the cluster of users.

View tracks - block/curr_admin:track:view

  • This allows a user to view tracks.
  • Assign this permission to users when they need to see tracks.
  • For example, if a role has permission to "create tracks", "view tracks" permission is needed to view the Manage Tracks page and Add track button.

Create users - block/curr_admin:user:create

  • This allows a user to create users.
  • Assign this permission in the system context.

Delete users - block/curr_admin:user:delete

  • This allows a user to delete users.
  • Assign this permission in the system, ELIS ,or user context.
  • For example, allow this permission and 'view cluster' permission in a cluster context, and users of the cluster could be deleted.

Edit users - block/curr_admin:user:edit

  • This allows a user to edit other users.
  • Assign this permission in the system, ELIS or user contexts.
  • For example, assign this permission and the 'view users' permission in a user context, and you could view the user and edit their profile.

View users - block/curr_admin:user:view

  • This allows a user to view other users.
  • Assign this permission in the system, ELIS , and user contexts.
  • For example, if a role has permission to create/edit/delete users, the role must have 'view users' permission for the other user permissions to work.

Can view learning plan - block/curr_admin:viewcoursecatalog

  • This allows a user to view the Learning Plan.
  • Assign this permission in the system context.

Can view reports for own group - block/curr_admin:viewgroupreports

  • This permission was used with older versions of ELIS, I believe prior to ELIS 1.9.
  • There is now a section in permissions called ELIS Report, use those permissions to give the user the capability to view/schedule ELIS reports.
  • To create a use case where a user can only see ELIS Reports for users in their cluster, assign the permissions to a user in a cluster context only. The permissions could also be assigned in a curriculum context, track context, etc.

Can view own reports - block/curr_admin:viewownreports

  • This allows a user to view their own reports.
  • Assign this permission in the system context.
  • For example, this permission allows a user to view their Individual User report.

Can view reports for all users - block/curr_admin:viewreports

  • This allows a user to view reports for all users.
  • Assign this permission in the system context.
  • For example, assign this permission and the 3 ELIS report permissions at the system level, and all the ELIS reports can be generated for all users.