Role-Based Access Control (RBAC) is an access control model that restricts system access based on a user's role within an organization.
In RBAC, access rights are assigned to roles, and users are then assigned to these roles. Instead of assigning permissions directly to individual users, users inherit the permissions of the roles to which they are assigned.
Tovuti has several features that allow administrators to adopt an RBAC system with their LMS. The benefits of implementing this type of access system include
- Enhanced Security
- Simplified Administration
- Audit and Compliance
- Scalability
This article outlines the following concepts and links to more detailed articles on how to implement each feature:
Admin roles and permissions
Top-level Admins (Site Administrators) can designate others as “Sub-Admins.” These sub-admins can then receive access to a portion of the Admin Portal. This allows each member of the Admin team to specialize in certain areas of the Admin Portal. It also delegates responsibility for certain tasks and tools to specific Admins.
User Groups
Begin by creating specific User Groups for these sub-admin types.
Go to People > click User Groups > click New
Create User Groups that correspond to each of the necessary Sub-Admin groups. This may include groups that correspond to tasks/features such as:
- Sub-Admin: Courses
- Sub-Admin: Events
- Sub-Admin: User Management
- etc
Or, Sub-Admin groups could correspond to segments of users, such as:
- Sub-Admin: HR
- Sub-Admin: Onboarding
- Sub-Admin: Communications Department
- Etc
Permissions by task/feature
Once the proper Sub-Admin user groups are built, go to People > click Admin Roles & Permissions > click New.
Give this Permission set a Title and select the corresponding user group of Sub-Admins. Configure all of the correct feature permissions.
For example, the “Sub-Admin: User Management” group is selected for this permission set. Then, all “People” features can be enabled. All other access to other features can be limited.
When configured in this way, all users who belong to the “Sub-Admin: User Management” user group can now access ONLY the People features in the Admin Portal. This allows them to complete User Management tasks and locks them from editing other configurations and features.
Permission by user segments
Admin Roles and Permissions can also be used to control which users a Sub-Admin can view and edit in the Admin Portal. This is done in the User Segments tab.
Give this permission set the necessary title, then in the User Segments tab, assign which users this Admin has access to.
User Teams
Admins can also delegate admin-type responsibilities to non-Admins through User Teams. Team Leads access team member information and administrative functions from the Team Lead Dashboard
Go to People > click User Teams > click New
In the Team Members and Leaders tab, set who is included in this team and who has the managerial role over these users.
In the Team Lead Permissions tab, set what actions the Team Lead can perform.
Instructors
When assigned to a Lesson, Instructors are a point of contact for Learners in Courses and Events. This creates a link that provides a human touch for users.
Go to People > Click Instructors> Click New
Provide the Name, Title, Image (suggested image size: 150x150 px), and optional social profile for this Instructor. Select a User to inhabit this instructor slot.
For the Instructor to be attached to a User, the User must first be created in the User Manager or imported in the User Importer.
Instructors can then be attached to Lessons or Events