What is role-based access control?

Roles scale because their number stays small while the number of people does not.

Joining and changing jobs both become one action. Assign a role, and the fourteen individual permissions come with it.

Drift is the standing problem. Somebody needs one extra thing, gets promoted to a wider role, and the exception is never reversed.

After a year or two everybody is an administrator and the model is decorative, which is the most common ending for a good permission system.

Roles also have to match how the work is really divided. A permission map copied from a larger company describes jobs nobody here does, and people route around it within a month.

Say you run an HVAC shop with eight people: you, an office manager, a dispatcher, four technicians and a part-time bookkeeper. You don't need eight sets of permissions. Three roles will do. Owner sees and changes everything, including billing and user accounts. Office covers your manager and your dispatcher, who read every transcript and edit bookings but can't touch billing or add users. Field covers the technicians, who see today's jobs and the call summary for each one, with no access to the full history.

Your bookkeeper doesn't fit, and that's the useful part of the exercise. She needs invoices and nothing about calls, so she either gets a fourth, narrow role or no account in the phone system at all. That second answer is usually right. When a technician becomes dispatcher next year, you change one field from Field to Office and you're done.

Open your user list and sort by role. Count the admins. If a small business has more than two, ask each one what they did last month that needed it. Usually the answer is one task, done once, in a hurry. Move them back down and note what the task was, because it tells you which permission your middle role is missing. While you're there, look for accounts with no login in 90 days.

Here's the cost of skipping this. A phished password is exactly as dangerous as the account behind it. When a technician's login is stolen and he's on the Field role, the thief sees a day of job summaries. Suppose he was bumped to admin last summer to fix a calendar setting. That same thief can now export every transcript you keep and create a fresh account to come back through.

Call records are sensitive, so the practical advice is to keep the number of people who can read transcripts small and deliberate.

Fewer accounts is the control that works without any configuration at all.

GreetKeeper holds no certifications, and we would rather describe what you can set than imply an audited permission model.