User Roles and Permissions

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

The front desk is the clearest example. A receptionist has to find a patient, book an appointment and move it when someone rings to change the time. She has no reason to see what the treatment cost, what the doctor wrote, or last month's income. Those are separate permissions, and a decent system lets you grant the booking without the rest. DocMz arrives with roles already shaped that way for clinics, because Linkysoft has watched the same argument happen in every practice.

The very common mistake is handing everyone the manager login. It starts for an honest reason. Something is urgent, the manager is out, and sharing the password is the quickest way through the day. Then it is never undone. From that point every action carries the manager's name, so when a price is changed or a record deleted, nobody can say who did it. The history is still there. It simply points at the wrong person.

There is a second cost that catches people out. When one login is shared, you cannot remove one person's access when they leave. 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, because a shared password undoes every other protection you paid for.

Two habits fix most of it. Give every person their own login, and give every role the least it needs to finish the job. If 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.