Guide
What can this user do? Effective permissions
See what a person's roles add up to, entity by entity, and which role gives each right, so you know which role to change.
This is part of Qorekit 0.3, out now as a beta: download 0.3.0-beta.1. As with any beta, keep a backup of anything you cannot afford to lose.
When someone says they cannot see a list, or can see too much, you need to know where their access comes from. Qorekit 0.3 shows it on the person’s details: everything their roles allow, and which role allows each part.
This post explains how roles combine and how to read the new What they may do section.
How roles add up
People get permissions through their roles. A person can have several roles, such as Sales and Support. When they do, they get the widest access of those roles together.
For each entity, a role sets these permissions:
| Permission | Choices |
|---|---|
| See | None, own, all |
| Add | Yes or no |
| Change | None, own, all |
| Delete | None, own, all |
| Export | Yes or no |
Own means the records the person created. If Sales gives See: own on deals and Support gives See: all, a person with both roles sees all deals. The wider of the two wins.
Roles can also give administration permissions, such as Manage choice lists or Import records from CSV. A person has an administration permission if any of their roles gives it.
A role marked Administrator can see and change everything, whatever else it says.
With two or three roles per person, working this out by hand means opening each role and comparing tables. That is where mistakes happen.
Reading What they may do
- Open Administration › Users.
- Select the person.
- Scroll to What they may do, at the bottom of their details.
It shows what their roles add up to:
- for each entity, whether they may see, add, change, delete and export records;
- the administration permissions they have.
Each right comes with the roles it comes from. Next to See: all on deals, you might read Support. Next to Import records from CSV, you might read Sales.
Using it to fix access
The section answers the question that matters when access is wrong: which role do I change?
Someone sees too much. Find the right they should not have, such as Delete: all on companies. The roles next to it are the ones to change. If two roles give it, you need to change both, or take one of the roles away.
Someone sees too little. Find the entity. If no role gives See, the entity is missing from their menu. Give the permission in one of their roles, or give them a role that has it.
Before you change a role, remember that it changes access for everyone who holds it. If only this one person needs more, a separate role may be the better fix.
A worked example
Suppose Ada works in sales and also helps with support. She has two roles:
- Sales: deals See: own, Change: own; companies See: all.
- Support: tickets See: all, Change: all; deals See: all.
Ada reports that she can see her colleagues’ deals, which surprises her manager. What they may do shows See: all on deals, coming from Support.
The fix is clear. Either Support should give See: none on deals, or Ada needs a different support role. Without the section, you would have had to open both roles and compare them line by line.
Checking the result
After changing a role, open the person’s details again. What they may do now shows what their roles add up to after the change.
To see the change as the person would, an administrator can open the role and choose View as this role. The post view Qorekit as a role covers that preview.
Who can see it
The section is part of a user’s details in Administration › Users. Administrators can open every user. People whose role has the permission Invite, edit and deactivate users can manage users too, within the roles they may give.
Only administrators can change roles themselves, in Administration › Roles.
Read more
The documentation describes what they may do on the users page, and every permission on the roles and permissions page. This section arrives with Qorekit 0.3.0.