Roles

A user role is a group of users who are granted identical permissions. Setting up roles is the quickest and most consistent way to apply the same set of permissions to multiple users who have similar responsibilities. You can grant all the permissions at the role level. Then, once the user is made a member of that role, the user inherits all that role’s permissions. Roles are created and managed on the Administration > Users & Roles > Roles page. When you create a new role, you name the role and then select the Upland Qvidian products the users in this role can use, and their system permissions. Once you set up your roles, you can now create your individual User IDs and assign the appropriate role(s) to each User ID.

Example: For an example of roles and permissions, see the "Example of Permissions by Role" section of Permissions.

Using the Everyone Role

The Everyone role is designed for situations in which you want to grant every user the same permissions. For example, if your company grants all its users the Change Password and Change Basic Personal Info (Address, Phone, etc.) permissions, you can use the Everyone role to quickly grant those permissions to all users rather than doing so individually. Then, all other permissions granted users are performed via standard role by role, or user by user basis. The Everyone role is a fixed role that cannot be removed. Please note the following considerations when using this role:

  • You can assign permissions and product licenses to this role just like any other role.
  • Any permission selected for this role will be granted to all users and cannot be removed for any user. If you do not want specific users to have a permission selected for this role, you would need to clear the permission and then grant the permission on a user by user basis.
  • Because all users are members of this role, there is no option to add or remove users.

ProSearch

ProSearch is a limited Upland Qvidian license with limited access to specific features for users who primarily work with content in the library and answer assigned questions in created documents. Administrators can assign a ProSearch license to users or roles by selecting ProSearch as the product in user properties under Role Memberships or in the role properties under Role Information.

Examples of ProSearch users include:

  • Subject Matter Experts (SMEs) could use it to easily respond to questions assigned to them from an RFP created document and/or submit new content suggestions.
  • Sales Reps may use it for general consumption of content needed in interactions with prospects.
  • Users who need access to library but no automation.

Permissions by Role Report

It is a common practice to design a plan for user, role and permissions prior to administrating them in Upland Qvidian. You can do this by running the Permissions - By Role report that prints all the permissions with the roles across the top and indicates which permission is applied to each role. If you have not created roles yet, the roles columns will be blank spaces that you can fill in with the roles you intend to create. You can also run the report with each new release to help you manage permissions.

Example of Permissions - By Role Report

Example of Permissions - By Role report. Click to enlarge.

Note: The License usage panel in the Roles page (Administration > Users & Roles > Roles), lists the Upland Qvidian application licenses that are available for use to help you make decisions when adding or removing users.

When working with roles permissions, keep in mind the following:

  • Adding or deleting a role permission changes it for all users assigned to the role.
  • You can add a permission for a role that has not been previously granted as a role permission, but you cannot remove a user permission for a user that was previously assigned to the user as a role permission.
  • A user can be assigned to more than one role and, therefore, role permissions may overlap. For example, a user is assigned to role 1 and role 2. Role 1 has permission A and permission B and role 2 has permission A and permission C , therefore, the user has A, B, and C permissions. If you removed permission C from role 2, then the user would have permission A and permission B. But if you removed permission A from role 1, the user would still have permission A, because it is given to the user by role 2.