Role-based access control explained without jargon
Role-based access control means you decide what a role may see and do, and then give each person a role. A role is a type of job, such as "Sales" or "Finance". You do not decide what Anna may see. You decide what Sales may see, and then you say that Anna is in Sales. The short form you will sometimes read is RBAC.
An everyday comparison
Think of the keys in a hotel. The cleaner's key opens the rooms. The cook's key opens the kitchen and the store room. The manager's key opens everything. Nobody decides door by door for each new employee. The hotel decides once what each job needs, and a new cleaner simply gets a cleaner's key.
Software works the same way. The "doors" are the customer list, the invoices, the staff records. The "key" is the role.
Why it matters to a small business
The other way is to set access person by person. That works with four people. With fifteen, nobody can say for sure who is able to open the salary list. The honest answer to "why can he see that?" is often "someone allowed it two years ago".
Roles keep this simple in three ways.
- New people are set up in a minute. They get a role, and that is all.
- Changes are one step. When Anna moves from sales to finance, you change her role.
- Mistakes do less harm. A wrong click or a stolen password can only reach what that role can reach.
A worked example for twelve people
Take a service company with an owner, an office manager who does the books, two team leaders and eight employees. Four roles are enough.
| Role | Customers | Invoices | Staff records |
|---|---|---|---|
| Owner | Everything | Everything | Everything |
| Finance | Look only | Create, change, approve | Pay details |
| Team leader | Look and change | Look, own projects | Own team, approve leave |
| Employee | Own customers | Nothing | Own record only |
Twelve people, four roles, one table that fits on a page. Nobody has to remember what the last new employee was given.
Looking is not the same as changing
The table shows two details that matter in daily work.
First, there is a difference between looking at something and changing or deleting it. The office manager may need to read customer details for an invoice. She does not need to delete customers.
Second, two people can have the same role and still see different things. Two salespeople are both "Employee", but each sees only their own customers. That is what "own" means in the table.
The rule behind all of this has a name: least privilege. It means each role gets what the job needs and nothing more. It is not a sign of distrust. It also keeps each person's screen free of things they never use.
Three mistakes to avoid
- Everyone gets the owner's role. It saves ten minutes at the start and removes every protection.
- One role per person. "Anna's role" and "Tom's role" bring back the old person-by-person lists.
- Nothing happens when someone leaves. Access should end on the last day, in one place.
Once or twice a year, read your role table again and ask whether each line is still true.
How Worknano handles this
Worknano manages access in one place for every part of the workspace, which it calls modules. A role decides which modules a person sees and what they may do in each one: read, create, change, delete, export, share or approve. It also decides which fields are visible, read-only or hidden. Further rules can narrow a role to a person's own records, or those of their team or division. A single person can be given access to one more module without changing their role. Changes to roles and permissions are logged with who did what and when. A module you add yourself gets the same permission settings automatically.
- Permissions: roles, access, and who can see what
- How to set who can read, create, or approve a record
- Organization: the structure that roles and approvals follow
Create a free workspace and turn your role table into working permissions.