Creating and editing a role
A role is the set of actions somebody is allowed to take. Learnient ships several and you build your own alongside them — and the screen is designed so that building one does not mean deciding two hundred things by hand.
For what a role decides and what it does not, read How roles and visibility work first. Visibility is a separate matter, and it is the reason a role can look right and still show somebody nothing.
Where it is
Section titled “Where it is”Choose Admin, then Workspace and Roles & permissions. The list shows every role with how many people hold it, split into System roles and Your custom roles.
Only custom roles can be edited. The system ones are templates, and the screen says so by making them unclickable rather than by refusing after you try.
Creating one
Section titled “Creating one”- Choose New role.
- Give it a name. It is required and it is what administrators will pick from, so name it after the job rather than the permissions.
- Pick a starting bundle, or copy an existing role.
- Adjust the grid.
- Save.
Start from a bundle rather than from nothing
Section titled “Start from a bundle rather than from nothing”The dialog offers eight starting points, each telling you how much it applies:
| Bundle | Permissions |
|---|---|
| Full manage | 229 |
| Create & edit (no delete) | 158 |
| Read-only | 82 |
| People & org | 75 |
| Content management | 70 |
| Reporting & analytics | 57 |
| Tenant settings | 35 |
| Gamification & home | 32 |
Copy from role does the same thing from a role you already have, which is usually the faster route once your account is established.
A bundle is a starting position, not a category you are joining. Applying it fills the grid and you then change whatever you like — nothing is locked afterwards.
The grid, and the three ways to use it
Section titled “The grid, and the three ways to use it”The legend is the whole instruction: column = action everywhere · row = full CRUD · cell = one permission.
- Clicking a column heading grants that action across every resource — every View, or every Delete.
- Clicking a row grants the full set for one resource.
- Clicking a cell grants exactly one permission.
Each column shows how much of it is on, as a count like 2/4 or 1/41. That is the fastest way to see what a bundle actually did, and the fastest way to spot a role that has one stray permission in an area it should not touch.
Search resources & permissions filters the grid, which is the only sensible way to find a single permission among hundreds.
Deleting a role
Section titled “Deleting a role”A role cannot be deleted while anybody holds it. You move those people to another role first, and the deletion then goes through.
Nobody ends up without a role, because a user cannot exist without one — which is why the reassignment is part of deleting rather than something to tidy up afterwards.
What happens when you save
Section titled “What happens when you save”Saving clears the cached permissions for the whole account, so the role applies to everybody holding it the next time they load the platform — not only to people you add later.
Somebody signed in when you narrow a role finds the controls gone where they were, which is worth timing if you are removing something people are mid-way through using.
One permission is not the whole story for one task. Importing people is a different permission from creating them, so a role that can do the obvious part of a job may still stop at the step nobody thought to grant.