User Roles and Permissions

User roles and permissions decide who may do what inside a system, so a receptionist can book an appointment without ever seeing what the treatment cost.

Also known as access rights user permissions role based access

Definition

A role is a job title inside the software, and a permission is one small thing a person is allowed to do. A role is therefore a bundle of permissions that you set up once and hand out, instead of ticking boxes again for every new hire. That is why the receptionist, the nurse, the accountant and the branch manager each see a different screen after logging in.

The front desk shows it best, because a receptionist must find a patient, book an appointment and move it when someone rings to change the time. What she does not need is the price of the treatment, the note the doctor wrote, or last month's income. Those are separate permissions, so a decent system can grant the booking and hold the rest back. That is how DocMz arrives for clinics, with roles already shaped that way, because Linkysoft has watched the same argument in every practice.

The most common mistake is handing everyone the manager login, and it always starts for an honest reason. Something is urgent, the manager is out, and sharing the password is the quickest way through the day. What nobody does is undo it afterwards, so from that moment every action carries the manager's name. Change a price or delete a record after that and nobody can say who did it, because the history is still kept but points at the wrong person.

There is a second cost that catches people out, because you cannot remove one person's access when they leave a shared login. You have to change the password and tell everybody the new one, which is why most businesses quietly never do. Linkysoft's cybersecurity work often begins here rather than with firewalls, since a shared password undoes every other protection you have paid for.

Two habits fix most of this, and the first is to give every person their own login rather than a shared one. The second is to give every role the least it needs to finish the job. So when a receptionist needs a price once a month, that is a question for the manager, not a reason to widen the role. Review the roles a month after going live, because the real shape of the work only shows once people are using it.

Questions about User Roles and Permissions

What is the difference between a role and a permission?
A permission is one action, such as booking an appointment. A role is a named bundle of permissions given to a job, so you assign the job once instead of setting every action by hand.
Why should a receptionist not see treatment prices?
Because the price is not needed for the booking, and every extra screen a person can open is another place a mistake or a leak can start. Give access by task, not by seniority.
What goes wrong when everyone shares the manager login?
Every action carries one name, so nobody can tell who changed a price or deleted a record. You also cannot cut off one person when they leave without changing the password for everyone.
How many roles does a small business need?
Three or four is usually enough at the start, one for each real job. Add another only when someone genuinely needs something no existing role covers.

Still not sure how this applies to your project?

Tell us what you are building and we will answer in plain language.