PLATFORM
Users Management
Manage individual accounts and assign permissions by role.
Who uses it IT administrators, HR and department managers
Why your business needs it
What goes wrong
Former employees can keep access, and shared accounts make ownership unclear. A shared login makes it hard to tell who changed a record. If nobody owns account reviews, staff can retain access after a move or departure.
When to add it
Several teams use erpWF, or staff join, move and leave often enough that account access needs a repeatable review.
What to measure
How long does it take to change an employee’s access and verify that their former role no longer applies?
Example business · Multi-branch retailer
A business walkthrough
A cashier moves to head office. The branch manager needs the store’s records, while the new head-office role needs a different view.
-
Define roles
List what each role should see
-
Assign permissions
Compare the permissions assigned to two individual accounts
-
Review access
Review access after the move and confirm who owns future changes
Role access
This diagram could not load. The key and walkthrough describe the same process.
- Padlock
- The permission boundary around a set of records
- Opening shackle
- Access granted to the selected role
Think of the lock as the permission boundary: change the role in the demo and compare which records it can open.