With Roles you can differentiate between what users can do and see on the platform. This way you can give extra permissions or rights to certain users based on their role in the organisation.

We have created four types of roles. You can create multiple roles per type, except for the Admin role:

  • Team Member
  • Team Leader
  • HR Officer
  • Admin


Team Member

The Team Member role is the default role for most of your users. They don't have any access to any platform configuration and mostly can't see any data beside that of their direct colleagues ( in some cases this can still be overwritten by visibility levels).


Team Leader

The Team Leader role is the default role for all users who lead a team. As with the Team Member role they don't have access to any platform configuration, but they can visualise and act upon the data of their team members.

For every Team Leader role you can decide whether they can manage their own team composition, i.e. add and remove users from their team; and set the hierarchy depth: a hierarchy depth of 0 means the team lead can only visualise data of their direct reports, 1 means they can visualise data of people who report to their reports etc...


HR Officer

The HR Officer role is meant for users who needs extra permissions or who need visibility rights surpassing the team level. Whether you want to create an IT Administrator role, a local HR role or a L&D role, the HR Officer role will make it possible to customise the amount of visibility and the proper permissions those people need.

For each module you can define a group of users, based on a set of criteria, for which you can give users of that role admin rights. This makes it possible to share responsibilities; or to report on a certain segment of your user base.


Admin

The Admin role is meant for users who need to be able to configure the platform and have access to user data for reporting purposes. This is mostly someone who's responsible for the implementation or the usage of the platform, or a senior member of the HR Team.



General Permissions

General permissions are permissions which have impact on the entire platform. They entail both configuration options and user management.


Team Members

Users with a Team Member role will have no access to any general permission.


Team Leaders

Users with a Team Leader role can have 3 specific general permissions:

  • Team hierarchy depth: you can set the hierarchy depth per Team Leader role. This way you can give users who are higher up in the hierarchy a different hierarchy depth than a line manager
  • Team leaders can manage their own teams: give users the option to add or remove users from their teams
  • Team leaders can create project teams (with the Project Teams feature): allow a user to create a project team.


HR Officers

Users with a HR Officer role can have permissions related to the platform configuration: theming, integrations, communication etc., and user management (add and manage users, teams or groups)


Admin

The Admin role has every permission enabled by default. It's not possible to disable those permissions.



Perform Permissions

Perform permissions are permissions related to features of the Perform module


Team Member

Users with a Team Member role will have access to the basic functionality of the Perform module.

  • Objectives: users can create personal objectives and visualise objectives of other users, depending on the visibility level on the objective.
  • Feedback/Praise: users can give or request feedback or send praise. They can view other users' feedback and praise, depending on the visibility level.
  • Conversations: users can plan and conduct conversations with their team leads and/or coaches. They can only view their own personal conversation history
  • Snapshots: users have no access to the snapshot results, nor can they fill in snapshots.


Team Leader

Users with a Team Leader role will have access to the team leader functionality of the Perform module.

  • Objectives: users can create personal objectives for themselves AND for their team members as well as create team objectives. They can also visualise objectives of other users, depending on the visibility level on the objective. In most cases this will mean they can visualise and report on the objectives of their direct and indirect reports, depending on the hierarchy depth
  • Feedback/Praise: users can give or request feedback, or send praise. They can view other users' feedback and praise, depending on the visibility level. In most cases this will mean they can visualise and report on the feedback/praise of their direct and indirect reports, depending on the hierarchy depth
  • Conversations: users can plan and conduct conversations with their team members. If the conversation template allows, they can also view conversations done by their direct reports. In most cases this will mean they can visualise and report on the conversations of their direct and indirect reports, depending on the hierarchy depth.
  • Snapshots: users can fill in snapshots about their direct reports. In most cases they will be able to visualise and report on the snapshots of their direct and indirect reports, depending on the hierarchy depth.


HR Officer

Users with a HR Officer role can have access to some admin functionality of the Perform module.

You can give users with this role admin visibility rights for the entire user base or for a certain segment. At the moment it's not yet possible to give permissions related to the configuration of the features. That is still the sole responsibility of the Admin role.

  • objectives: users can create team objectives, and personal objectives for themselves, for their team members and for the selected segment/entire organisation. They can also visualise every objective regardless of visibility level within the assigned segment.
  • Feedback/praise: users can give or request feedback, or send praise. They can view other users' feedback and praise, depending on the visibility level.
  • Conversations: users can plan and conduct conversations with their team leads/team members or coaches/coachees. If the conversation template allows, they can also view conversations done by other users from within their assigned segment.
  • Snapshots: users can fill in snapshots about their direct reports. They can visualise the results and report on the snapshots of their direct and indirect reports, as well as users from within their segment.

Admin

Users with the admin role have access to the full admin functionality of the Perform module.

  • Objectives: users can create personal, team and organisational objectives for everyone on the platform. If the setting allows it, they can also visualise every objective.
  • Feedback/praise: users can give or request feedback or send praise. They can view other users' feedback and praise, depending on the visibility level. In most cases this will mean they can visualise and report on the feedback/praise of their direct and indirect reports, depending on the hierarchy depth
  • Conversations: users can plan and conduct conversations with their team leads/team members or coaches/coachees. If the conversation template allows, they can also view conversations done by other users.
  • Snapshots: users can fill in snapshots about their direct reports. They can visualise the results and report on the snapshots of everyone on the platform.


Engage Permissions

Engage permissions are permissions related to features of the Engage module.


Team Members

  • Engagement surveys: users can fill in received engagement surveys
  • Engagement Results: users have no access to the engagement results by default, but you can enable access for this role. If the setting is enabled they will have access to the Engagement Overview. Data is restricted to the teams they're part of.
  • Engagement Comments: users can leave comments/feedback on their engagement surveys and follow up on them


Team Leaders

  • Engagement surveys: users can fill in received engagement surveys
  • Engagement Results: users have access to the engagement results by default, but you can disable access. If access is enabled they will have access to the Engagement Overview and Insights. Data is restricted to the teams they're (in)directly leading.
  • Engagement Comments: users can leave comments/feedback on their engagement surveys and follow up on them. Users can reply to the comments of their team members, if this setting is enabled for the role.


HR Officer

You can give users with this role admin visibility rights for the entire user base or for a certain segment. At the moment it's not yet possible to give permissions related to the configuration of the features. That is still the sole responsibility of the Admin role.

  • Engagement surveys: users can fill in received engagement surveys
  • Engagement Results: users have access to the engagement results by default, but you can disable access. If access is enabled they will have access to the Engagement Overview and Insights. They can visualise the data of the teams they're (in)directly leading as well as the assigned segment or the entire organisation depending on what's chosen.
  • Engagement Comments: users can leave comments/feedback on their engagement surveys and follow up on them. Users can reply to comments from users from within their segment or from the entire organisation, depending on what's chosen.


Admin

  • Engagement surveys: users can fill in received engagement surveys
  • Engagement Results: users always have access to the engagement results by default. They will have access to the Engagement Overview and Insights. They can visualise the data of the entire organisation.
  • Engagement Comments: users can leave comments/feedback on their engagement surveys and follow up on them. Users can reply to comments from every user.


Learn Permissions

Learn permissions are permissions related to features of the learn module. Because of legacy reasons, every type of role can have the ability to create or manage courses, tracks and sessions.


Team Member

By default users with this role will have access to the Learn Library and My Learning. However, you can fully customise this role to give access to the Studio options. This way every user can create and manage courses, tracks and/or sessions.


Team Leader

By default users with this role will have access to the Learn Library and My Learning. They can also follow up on the progress of their direct reports and subscribe them to learning material. However, you can fully customise this role to give access to the Studio options. This way every user can create and manage courses, tracks and/or sessions.


HR Officer

As with Perform and Engage permissions, you can assign a segment to this role or select 'everyone'. This will make it possible to manage the learning of the assigned users.

You can also fully customise this role to give access to the Studio options. This way every user can create and manage courses, tracks and/or sessions.


Admin

Users with the admin role have access to every Studio option to create, edit or delete learning material.