Skip to main content

Roles and domains explained

This article explains how roles and domains relate to permissions, access, and actions.

Updated over 2 months ago

Role and domain access levels

Access levels depend on two features:

  • Role
    Comes with role-based permissions, such as creating users or running reports

  • Domain access
    This defines where you can use your permissions. Domain content can include users, Learning Paths and modules, reports, audience groups, and email templates

You can have multiple roles and domain access levels. Each are linked, so it's not possible to have a role without domain access, or domain access without a role.

Examples

You have three content domains:

  • Content - Skillcast London

  • Content - Skillcast Malta

  • Content - Skillcast Greece

You give a colleague based in London:

  • The role: Content Editor

  • Access to the domain: Content - Skillcast London

When your London colleague logs in, they can access content management and manage content in the domain Content - Skillcast London:

You also give a colleague based in Malta:

  • The role: Content Editor

  • Access to the domain: Content - Skillcast Malta

When your Malta colleague logs in, they can access content management and manage content in the domain Content - Skillcast Malta.

A manager of both colleagues may need to manage content on both domains. So their role may be a Portal admin, with permissions to access all content domains:

Drawing2.png

By giving colleagues in different locations access to different domains, you can restrict access to user data in each region. Then, if you change the colleague's role, such as to a Reporter, they can only report on the same domain.

Related articles

Did this answer your question?