Skip to main content

Managing roles & permissions across users

This article explains how to control what different users can see and do in Verity by creating company roles, setting their scope, and selecting the permissions those roles grant.

Written by Richard Lombos

What “roles”, “scope”, and “permissions” mean

Roles

A role is a reusable access profile (e.g., Member, Team Lead, Administrator) that you assign to users. Roles help you standardize access across teams instead of configuring each user individually.

Scope

Scope defines where a role’s permissions apply (e.g., only the user’s own items vs. the whole company). Scope doesn’t grant access on its own—it limits the reach of the permissions you select.

In Verity, scope follows an inheritance ladder:

Self → Group → Sub-region → Region → Company

Meaning: broader scopes include the levels beneath them.

Permissions

Permissions define what actions a user can take within a module (for example: View vs. Create, edit and delete).

Where to find Permissions in the navigation

From the left sidebar, go to:

Organization setup → Permissions

View existing roles

On Manage company roles & permissions, you’ll see a list of roles with:

  • Company role (role name)

  • Scope (where permissions apply)

  • Summary (count of permissions in that role)

Example roles you may see:

  • Member (Default) with Self scope

  • Administrator with Self, Group, Sub-region, Region, Company scope

  • Team Lead with Self and Group scope

Create a new role

  1. Go to Organization setup → Permissions.

  2. Click Add new role.

  3. Enter a Role name (use a clear naming convention like Team Lead (Region A)).

  4. (Optional but recommended) Choose a Role template

    • Templates let you start from an existing role so permissions and coverage are pre-filled, then you adjust what’s different.

  5. Click Save when finished.

Configure role scope

In the Scope section, choose where this role should apply:

  • Self: Items the user owns or sessions they participated in.

  • Group: Any groups where the user is a member.

  • Sub-region: Any sub-regions where the user is a member.

  • Region: Any regions where the user is a member.

  • Company: Everything across the organization.

Custom set (targeted access)

Use Custom set to add specific groups the user can access in addition to what their scope already covers. This is useful when someone needs access to a particular group outside their normal membership structure.

Configure permissions (what each permission area does)

In the Permissions section, each row is a module. Expand a module to choose actions like View or Create, edit and delete (action names can vary by module).

  1. Scorecards

    1. Used to evaluate conversations against defined criteria.

  2. Definitions

    1. Terms that require further explanation and can increase the accuracy of the evaluations.

  3. Knowledge Repository

    1. Reference materials that can inform configuration (e.g., when creating bots or scorecards).

  4. Bots

    1. Practice bots used for role-plays and training experiences.

      • View / use: Run or access bots.

      • Create (if available): Build and manage practice bots.

  5. Reports

    1. Aggregated reporting to understand performance respecting the role's scope.

  6. Organization Management

    1. Controls organization structure (regions/sub-regions/groups).

  7. User Management

    1. Invite and manage users in your Verity workspace.

  8. Role Management

    1. Manage company roles and permissions (this page and related capabilities).

Using “Select all” and expand controls

  • Expand (chevron): Shows the available actions inside each module.

  • Select all: Enables all actions for that module at once (use sparingly; it’s easy to over-grant).

Did this answer your question?