Roles
Roles give users control over what they can and can't do in the software. Roles are assigned to users.
Role categories
There several roles divided between two role categories:
Administrative roles category
Functional roles category
The following table shows each role and the category to which the role belongs.
Role | Administrative Category | Functional Category |
|---|---|---|
Company Admin | X | |
Customer Admin | X | |
User Manager | X | |
Desktop User | X | |
Dashboard Viewer | X | |
Transactions with PII | X | |
Transactions without PII | X | |
Portal Viewer | X | |
Theme Editor | X |
Administrative roles
These are the roles in the administrative category:
Customer Admin. Privileges to manage users and view dashboards within their assigned customer.
Company Admin. All privileges for Customer Admin plus privileges to view dashboards, view customers, and manage users within their assigned company.
User Manager. Provides access to the Manage Users page. This role must be assigned by Intellicheck support.
Each role is granted certain privileges. Privileges are applied on the Hub software interface through the addition or removal of menus and commands.
For example, a user assigned to the Customer Admin role sees the Users menu on the Hub interface.
Actions
Roles enable actions.
Actions include commands such as edit, activate and deactivate.
Administrative role priorities
You can assign more than one administrative role to a user. Privileges for higher-priority roles replace those for lower-priority ones. For example, the Company Admin role is a higher-priority role than the Customer Admin role. Therefore, Company Admin privileges are given to a user who is assigned both the Company Admin role and the Customer Admin role.
A user with a lower-priority role cannot edit another user with a higher-priority role. For example, a user assigned to the Customer Admin role cannot edit a user assigned to the Company Admin role.
Administrative roles and customer assignments
A user must be assigned to a customer. The customer assignment is limited based on the administrative role of whoever is adding or editing the user.
A Company Admin can assign a customer to a user. For example, suppose a Company Admin manages the Universal Widgets company, which has two customers, Witty Widgets and Wacky Widgets. That Company Admin can create a new user and assign the user to either Witty Widgets or Wacky Widgets.
A Customer Admin cannot assign a customer to a user. The assignment is automatic. For example, suppose a Customer Admin is assigned to the Witty Widgets customer. If that Customer Admin creates a new user, the new user is automatically assigned to Witty Widgets.
Functional roles
There are several functional roles:
Dashboard Viewer. Can view customer dashboards and reports.
Portal Viewer. Can access Portal to perform ID validation.
Desktop User. Can access the Products page to download and install Desktop software for ID validation. There is a separate log in URL for Desktop. The Desktop User role allows a Hub user to also log in to Desktop with the same Hub credentials.
Transaction with PII. Can view transactions and personally identifiable information (PII) for transactions.
Transactions without PII. Can view transactions, but not personally identifiable information (PII) for transactions.
Theme Editor. Can view and edit themes in Theme Builder.
Similar to administrative roles, each functional role is granted certain privileges. Privileges are applied on the Hub software interface through the addition or removal of menus and commands, as shown in the following table.
Functional role privileges
Role | View customer dashboards | View customer journey data | View transactions but not PII | View transactions and PII | Use Portal to perform ID validation | Log in to Desktop (separate URL) | Download Desktop | View and edit themes |
|---|---|---|---|---|---|---|---|---|
Dashboard Viewer Role | Yes | Yes | No | No | No | No | No | No |
Transactions with PII Role | Yes | Yes | Yes | Yes | No | No | No | No |
Transactions without PII Role | Yes | Yes | Yes | No | No | No | No | No |
Portal Viewer Role | No | No | No | No | Yes | No | No | No |
Desktop User Role | No | No | No | No | No | Yes | Yes | No |
Theme Editor Role | No | No | No | No | No | No | No | Yes |
For example, a user assigned only to the Portal Viewer role can only use Portal to perform ID validation. Therefore, when that user is logged in, the Portal menu appears on the Hub interface. But no other menus appear.
Assign roles
When you add a user or edit a user, you can assign roles.
A user can be assigned a single role or multiple roles.
Example role assignments
User | Company Admin | Customer Admin | User Manager | Desktop User | Transactions with PII | Transactions without PII | Dashboard Viewer | Portal Viewer | Theme Editor |
|---|---|---|---|---|---|---|---|---|---|
Bob | X | X | X | ||||||
Alice | X | X | X | X | |||||
John | X | X | X | X | |||||
Jane | X | X | X | ||||||
June | X |
Bob is a Company Admin with functional roles for Dashboard and Portal. Bob can view customers (but not create or edit customers); view, create, and edit users; view dashboards; and use Portal. But Bob cannot log in to Desktop.
Alice is a Customer Admin with functional roles for Desktop, Transactions without PII, and Dashboard Viewer. Alice can view, create, and edit users; log in to Desktop; and view transactions but not PII on the Transactions page. Alice cannot use Portal.
John is a Customer Admin with functional roles for Transactions with PII, Dashboard, and Portal. John can view, create, and edit users; view transactions with PII; view dashboards; and use Portal.
Jane has no administrative roles, but has three functional roles for Desktop, Portal, and Theme Editor. Jane can log in to Desktop, use Portal, and select the Themes menu to edit themes.
June is assigned a User Manager role. This role must be assigned by Intellicheck support. June can add, edit, and manage users.