Skip to main content
All CollectionsPeople
Role-Based Permissions Overview
Role-Based Permissions Overview

Role-based permissions let you designate which team members can perform which actions using role-based permissions in Opus.

D
Written by David Lamont
Updated over a month ago

Role-based permissions give you control over what actions a team member can take in Opus, as laid out by their role. By default, all users in Opus fall into one of three groups: Admins, Location Managers, and Trainees.

Admins

These are typically senior managers and executives - people who manage Opus across the organization. They must be invited by another Admin.

Click here to learn how to invite an Admin.

Location Managers

These are usually leaders of your frontline employees - general managers, location supervisors etc. Location Managers must be invited by an Admin.

Click here to learn about inviting someone as a Manager.

Trainees

Trainees are the end user of the Opus for Training mobile app — these are your frontline employees who will be completing modules, courses, and referring back to the app for access to shared files.

Trainees only have access to the app and they can only see material that has been assigned to them. Trainee information is only visible to Admins and Managers of their locations.


How to Create Role-Based Permissions

To create a new role-based permission, go to "Roles" under "People" in the main navigation.

  • Click "+ New Role"

  • Choose whether this role is an Admin, Location Manager, or Trainee.

  • From there, you'll be able to designate permissions associated at the Admin or Location Manager level.

    • For those permissions to take effect, you will need to assign users to that role. To learn how to assign roles to team members, click here.

To edit an existing role's permissions and user type:

  • Select the role you're trying to edit in the lefthand navigation.

  • Click "Edit role"

  • Change user type and permissions

  • Save!


Understanding Permissions

By default, the following permissions are available across all Admins & Managers unless designated otherwise.

Permission

Admin

Location Manager

Definition

Change Org Settings

Access to Billing, Compliance, Languages, Email, and Brand

Manage Org Integrations

Access to HRIS Integration

Manage Billing

Access to Settings > Billing, Ability to purchase credits

Invite Others

Permission to invite other team members to Opus.

Create Content

Permission to create content in Opus.

Manage Library

Permission to manage content in the Library and create paths.

Assign Content

Permission to assign content and mark assignments as complete.

Unassign Content

Permission to unassign content.

Update Automations

Permission to create Automations. Note: Automations are managed at the org-level.

View Reporting

Access to Reporting in dashboard. Note: users without this permission will not see the reporting tab at all.

Send Messages

Ability to send messages. Users will still be able to see all messages sent across the org/their location.

Edit Trainees

Ability to edit trainee profile.

Deactivate Trainees

Ability to deactivate a trainee.

Manage Premium Content

Ability to purchase, set up, configure, assign premium content (whether or not it’s already in the library).

Promote Trainees

Ability to promote employees.

Update Automations and Library Access

Ability to create and manage assignment automations, library access, and paths.

Note: Modules do not currently have permissions set. They are open to both admins and managers. Therefore managers can add content to modules even though they cannot edit the content that they have created.


User-Specific Overrides

In cases where you need to disable or enable permissions on a user-level, you can set a user-specific override.

  • Go to People or search for the employee using the Search bar

  • Click into that employee's profile

  • Click to view Permissions

  • Hit "Override user permissions"

    • Select "Always" to give that user access

    • Select "Never" to remove that user's access

  • Hit "Save"!

Did this answer your question?