Skip to main content

User Roles & Permissions

Understand the four user roles in Lumofy, what Admins and Managers can access by default, and how to extend access with Permission Sets.

Written by Mohamed Shantory

Before You Start

  • Roles and permissions are managed under Settings → Company Settings → Roles & Permissions.

  • To edit the Manager role and Permission Sets, you need the Manage roles and permissions permission. Super Admins and Admins have it by default.

  • To edit the Admin role, you need the Manage primary roles permission. Only Super Admins have it by default.


Overview

Every Lumofy user has one of four roles: Super Admin, Admin, Manager, or Talent. Admin and Manager are the two primary roles, and their permissions can be configured. On top of the primary role, you can create Permission Sets: custom bundles of access that you assign to specific users when their primary role doesn't cover what they need.


The Four Roles

Super Admin

The Super Admin owns the Lumofy environment and has full, unrestricted access to every area of the platform. Super Admin permissions are locked and can't be edited.

💡 Tip: Give Super Admin access only to the people who own or fully operate the platform. It can't be scoped or limited.


Admin (primary role)

Admins manage the platform. By default, the Admin role holds every permission across the platform, including the Dashboard, with two exception: Certifications and Manage primary roles.

This means Admins can edit the Manager role and manage Permission Sets through Manage roles and permissions, but they can't edit the Admin role. The Manage button next to Admin appears disabled for them. An Admin who is granted Manage primary roles can edit the Admin role as well.


Manager (primary role)

Managers work with their own team. By default, the Manager role can view most areas, and most of its permissions are limited to Own Team Only. The full list is in Default Manager Permissions below.


Talent

Talent is the end-user role. Talent permissions are fixed and can't be edited. Talents can:

  • Access their assigned learning items in the Develop area

  • View and work on their Performance Sheet during active cycles

  • Set and track their Smart Goals

  • Acknowledge their performance results

  • Submit an Appeal if the cycle allows it

  • View the Leaderboard and see XP scores

Self-enrollment in learning: By default, Talents are assigned learning content by Admins. However, if the Admin enables self-enrollment, Talents can browse and enroll in available content on their own.


What Permissions Cover

Permissions are grouped by area and apply across the whole platform:

Area

Permission groups

Company

Dashboard, Company Profile, Company Structure, Users Management, Company Templates, Settings

Skills

Competencies (framework, clusters, competencies, analysis), Workforce Intelligence Map

Learning

Pathways, Content Lab (courses, kits, games, guides, bites, quizzes), Sessions, Leaderboard

Performance

Performance Management (cycles, goals, results, calibration, appeals)

Engagement

Engage (eNPS, surveys)

📝 Note: Mapped roles and expected levels in the competency profile are controlled by the Edit Company Structure permission.

Permission scope

Some permissions have a scope dropdown with two options:

  • Own Team Only: the permission applies to the user's own team.

  • All Talents: the permission applies to everyone in the company.

Some action permissions depend on their related view permission. They stay greyed out until the view permission is set to All Talents. For example, Manage Job Levels, Edit Company Structure, and Delete from Company Structure become available only when View Company Structure is set to All Talents.


Default Manager Permissions

The table lists the permissions the Manager role has by default. Anything not listed is off.

Group

Granted by default

Scope

Dashboard

View Dashboard Analytics

Own Team Only

Company Profile

View Company Profile

—

Company Structure

View Company Structure

Own Team Only

Workforce Intelligence Map

View Workforce Intelligence Map

Own Team Only

Users Management

View Users List

Own Team Only

Competencies

View Framework

Own Team Only

Pathways

View Pathways

—

Pathways

View Enrollments, Enroll Talents

Own Team Only

Content Lab

View Content List

—

Content Lab: Courses, Games, Quizzes

View Enrollments, Enroll Talents

Own Team Only

Sessions

View Sessions

—

Sessions

View Enrollments, Invite Attendees

Own Team Only

Company Templates

View Certificates

—

Leaderboard

View Leaderboard

—

Engage

View eNPS, View Surveys

Own Team Only

Managers have no Performance Management or Settings permissions by default

📝 Note: Performance Management permissions control the cycles themselves, such as creating, editing, or calibrating them. They don't affect a manager's ability to review their direct reports in an active cycle.


How Primary Roles and Permission Sets Work Together

  • One primary role per user. A user can be an Admin or a Manager, not both.

  • Multiple Permission Sets per user. A user can be assigned to as many Permission Sets as needed.

  • The primary role is the baseline. A Permission Set can't remove access that the user's primary role already grants.

  • Permission Sets only add access. Anything the primary role doesn't grant can be given through a Permission Set.

Example: adding access. Managers can't edit the company structure by default. Create a Permission Set that includes Edit Company Structure and assign it to the managers who need it. Other managers keep their default access.

Example: access that can't be removed. Managers can view the users list of their team by default. If you assign a manager to a Permission Set that doesn't include View Users List, they still have it through the Manager role.

Example: limited access for Talent. To let an employee run your annual eNPS or engagement surveys, create a Permission Set with only the eNPS and survey permissions and assign it to them. Their Talent access stays the same; they gain the extra access only.

Example: a role-specific set. A Performance Managers set can grant the Performance Management permissions to people who run review cycles but shouldn't touch learning content or company structure.

⚠️ Warning: To restrict access for a group of users, change the primary role's permissions. Leaving a permission out of a Permission Set doesn't restrict anyone.


Editing a Primary Role's Permissions

  1. Go to Settings → Company Settings → Roles & Permissions.

  2. Under Primary Roles, click Manage next to Admin or Manager. The role's permissions screen opens.

  3. Tick the permissions you want to grant and untick the ones you want to remove.

  4. For permissions with a scope dropdown, select Own Team Only or All Talents.

  5. Click Save Changes. A confirmation warning appears.

  6. Confirm to apply the change.

💡 Tip: Click View users with this role before saving to see who the change will affect.

⚠️ Warning: Changes to a primary role apply to every user with that role as soon as you confirm.


Creating a Permission Set

  1. Go to Settings → Company Settings → Roles & Permissions.

  2. Under Permission Sets, click + Create Permission Set.

  3. Enter a name for the set (for example, Performance Managers) and an optional description.

  4. Tick the permissions the set should grant, and select a scope where available.

  5. Scroll to the Assign Users section at the bottom of the page, click + Select Users, and choose the users to assign.

  6. Click Create Permission Set and confirm the warning.

💡 Tip: Name sets after the job they enable, so it's clear why a user was assigned to them.

⚠️ Warning: Manage roles and permissions and Manage Authentication give control over platform access and sign-in. Add them to a set only for users who need that control.

Assigning Users to an Existing Permission Set

  1. Under Permission Sets, click Edit next to the set.

  2. Scroll to the Assign Users section at the bottom of the page.

  3. Click + Select Users and choose the users to add.

  4. To remove a user, click Remove next to their name.

  5. Click Save Changes.

Assigned users receive the set's permissions in addition to their primary role.

Removing a Permission Set

  1. Under Permission Sets, click Remove next to the set.

  2. Confirm the removal.

⚠️ Warning: Users assigned to the set lose the permissions it granted. Their primary role access doesn't change.


FAQs

Can a user be both an Admin and a Manager?

No. Each user has one primary role. To give a Manager extra access, assign them a Permission Set.

Can I use a Permission Set to restrict an Admin or Manager?

No. Permission Sets only add access. To restrict access, remove the permission from the primary role.

Why are some permissions greyed out?

They depend on a related view permission. Set that view permission to All Talents and the greyed-out permissions become available.

Why can't I edit the Admin role?

Editing the Admin role requires the Manage primary roles permission. Admins don't have it by default. Once an Admin is granted it, they can edit the Admin role.

Can I give a Talent access to an admin area?

Yes. Assign the Talent a Permission Set with the permissions they need. Their Talent access doesn't change.

Can I edit Super Admin or Talent permissions?

No. Super Admin always has full access, and Talent permissions are fixed.

Did this answer your question?