Skip to main content

Roles

Explanation of the type of roles

K
Written by Katie Airey
Updated over a month ago

The explanations of the difference in roles:

User Role

Basic access for employees to read and acknowledge policies. ​

What Users Can Do: ​

  • View assigned policies based on groups or location. ​

  • Read and navigate policy content. ​

  • Acknowledge policies as read and understood. ​

  • Print/export policies as PDFs. ​

  • Translate policies using browser tools. ​

  • Customize reading experience (e.g., background colors). ​

  • Track personal compliance (due dates and unread policies). ​

What Users Cannot Do: ​

  • View others' compliance status.

  • Access compliance dashboards or reports.

  • Create, edit, or manage policies. ​

  • Change policy settings or assign policies. ​


Manager Role

The manager role can monitor compliance for their teams.

What Managers Can Do: ​

  • All User capabilities. ​

  • View compliance dashboards to track team compliance. ​

  • Monitor team compliance (read, unread, overdue policies). ​

  • Search/filter compliance data by employee or policy name, type, or category. ​

  • View user lists for policies (assigned, completed, overdue). ​

  • Change policy due dates for specific employees. ​

What Managers Cannot Do: ​

  • Create, edit, or publish policies. ​

  • Access policy settings or system configurations.

  • Modify policy types or organizational settings. ​

  • View compliance data beyond their permissions (set by Administrators). ​


Editor Role

The role of editor can create, edit, and publish policies.

What Editors Can Do:

  • All Manager capabilities. ​

  • Access the policy management interface. ​

  • Create new policies (from scratch or templates) with rich text formatting, personalized fields, and due dates. ​

  • Upload and convert documents (e.g., Word, PDF) into policies. ​

  • Save drafts and submit policies for review. ​

  • Edit existing policies and compare versions. ​

  • Publish policies (directly, from review, or in bulk). ​

  • Archive outdated policies. ​

  • Assign policies to user groups and set deadlines. ​

  • Manage policy versions and review schedules. ​

What Editors Cannot Do: ​

  • Access policy settings or system configurations.

  • Create/modify policy types or templates. ​

  • Manage user compliance permissions. ​

  • Access organisational settings


Administrator Role

The Administrator role includes: Full system control and configuration.

What Administrators Can Do: ​

  • All User, Manager, and Editor capabilities. ​

  • Manage policy settings (create/edit/delete policy types, assign editors, set default durations). ​

  • Create/edit/delete policy templates for reusable structures. ​

  • Manage personalized fields (e.g., auto-populated tags like employee name, location). ​

  • Configure compliance permissions for Managers and Editors (e.g., location-based, hierarchy-based). ​

  • Manage organization-wide settings (analytics, reporting, onboarding workflows). ​

  • Oversee all users, roles, and compliance data. ​

  • Modify any policy at any stage. ​

  • Control system-wide configurations (e.g., divisions, cross-division access). ​

🤓Tip: Administrators can restrict Manager and Editor access by location, hierarchy, policy type or group.

Did this answer your question?