The trouble with generic roles
Generic roles are easy to set up, but they force a choice. Either staff get extra access so they can work, or they are blocked from something they need and end up asking a colleague. The first exposes data for no reason. The second slows everything down.
Start from the task, not the job title
Instead of asking "what can a therapist do?", ask "what does this person do in their day?" A speech therapist in the clinic needs something different from a day-program therapist, and a branch manager something different from the general manager.
- Viewing is not editing. Whoever sees a report does not necessarily change it.
- Deleting is a separate permission, given to as few people as possible.
- Financial and HR data is kept apart from the clinical file.
Enforce it on the server
Hiding a button is not enough. If a permission is checked only in the interface, the data can be reached in other ways. Real permissions are checked on the server with every request.
Review permissions when the team changes
Someone moves departments, a substitute covers for two weeks, an employee leaves. Every change in the team should come with a change in permissions.
How this works in Enable 360
The system has 253 granular permissions across 81 modules, enforced in the interface and on the server. It supports multiple branches and unlimited users, so each person can get exactly what they need.
Security & rolloutFrequently asked questions
How many permissions does Enable 360 have?
253 granular permissions across 81 modules.
Is hiding screens from a user enough?
No. Permissions must also be checked on the server, which Enable 360 does.
Is there a limit on users in Enable 360?
No. Users are unlimited, with support for multiple branches.
Last reviewed:
