This document is designed as a complete reference for roles and permissions in Bridge. This document specifically discusses account-level and subaccount-level permissions. Using the information in this document, you may be able to troubleshoot permissions-related questions from your users or create custom roles for your account. 

Permissions by Feature

Accounts

Users

Groups

Content

Surveys

Reports

Marketplace

Permissions by User Role

Account Admin

Admin

Author

IT Admin

Manager

The Bridge roles and permissions feature allows for over 100 permission line items to be customized for any set of users. Bridge has five default user roles: Employee, Author, Admin, IT Admin, and Account Admin. All users added to Bridge are given the Employee role by default. Users can be assigned more than one default role, but adding a user to additional roles will only expand the permissions of that user, not restrict.

Each default permission allows a certain degree of customization. Custom roles can be created based on an existing default user role, and the custom role will inherit the default permissions of the user role it is based on. Custom roles can be used to modify default roles without any restrictions.

Manager roles are automatically created via CSV import. Admins can limit a manager’s default permissions but cannot give the Manager role additional permissions. Limiting a manager’s permissions takes away the manager’s ability to author content and enroll learners. Additional permissions can only be given to managers by assigning them an additional role like Admin or Account Admin.

By default, Authors can edit all course content within an account. To limit an Author's permissions to only editing the content that they create, contact your CSM or Support team.

Best Practices

• Begin by using the default user roles and permissions when setting up permissions in your Bridge instance. If the default permission sets do not fit a particular need, try to modify existing default roles. If the default roles cannot be modified to satisfy the need, then consider building a custom role.
• Use a short, concise naming convention for custom roles.
• Pilot custom roles to smaller test groups to vet custom roles, then expand to additional users when you are satisfied with the custom roles. Note that when creating a custom role, some permissions need to be enabled for other permissions to work correctly (e.g. a user must have the View Users permission enabled for the Enroll/Unenroll permission to work correctly).
• At any time, an individual with the appropriate permissions can delete a custom role. Default roles cannot be deleted.
• If a user only has a single role that is custom and that custom role is deleted, the user will inherit the roles of the learner. With this in mind, ensure that the users that have the ability to delete custom role is carefully considered.

Subaccount Permissions and Settings

The following account settings can be modified at the subaccount level and can be unique to each subaccount:

• Content Branding
• Account Configuration
• User Management (Auto CSV, HRIS, etc.)
• Roles & Permissions
• Notification Preferences

Important: This document matches the content shown in the Roles and Permissions page and is subject to change.