Role-Based Permissions for Staff at Learning Centers

How it works

1. 1. 1

      Give every staff member a security role

      Security Role is required when you add staff from Staff → Staff Info or a user from Admin → Users. Invite User sends someone an email to set their own password with the role you chose, though Admin is not offered there. No one can change their own security role, however senior.

   2. 2

      Set what each role can do

      Pick a role in Security Permissions and its grid loads: one row per module, page and function, with View, Create, Edit, Delete and All toggles. Turning off View also turns off the rest of that row, and some rows relabel Edit as something more specific, like Download for class notes and recordings. Filter by module, page or function, then Save or Discard Changes.

2. 3

   Require two-factor authentication by role

   The Two-Factor Authentication button lists every role with a Method of None, Email or SMS. Once a role has a method, everyone in that role must complete the second step when they log in. This option is turned on for your account on request, so ask support if you do not see the button.

   
3. 4

   Choose who can read the activity log

   Activity Permissions sets which roles can see each category of the activity log: Billing, Payment, Enrollment, Staff Info, Approvals, Student/Family Info, Student Assignment and Student Assessment. Pick one or more roles for each, separately from the main grid.

   
4. 1. 5

      Document it and extend it to mobile and files

      Export the grid to Excel or CSV, filtered to the module you want on record. In System Config, Mobile Permissions grants or removes each mobile app screen per role, Attachments Config sets who can add, view, download or delete course, level and challenge files, and Reports Config picks who can view the Result and Staff reports.

Who uses it