Module 3
Employees, roles and permissions
Person, employee and engagement, source processes and how permissions are assigned automatically or manually.
Lessons
1. Person, employee and engagement
The person is the only independent building block. An employee arises through an engagement – employment, assignment, placement or elected office – and can be created in HR, procurement or education processes. Supplier engagement is not the same as consultant.
The same person can hold several engagements at once, for example permanent employment and an elected office. That is why the engagement, not the person, carries unit, position and period.
- Person: identity that exists independently of the organisation.
- Engagement: the relationship to the organisation, with type, start and end.
- Employee: the person in the role of working in the organisation.
Example
A nurse has a fixed-term employment on a ward and is also elected to a committee. Two engagements, one person – and two different bases for permissions.
2. Several source processes – one combined view
A large public organisation often has several HR systems, and external resources are registered in procurement or contract processes. Trainees come from education processes and elected officials from the political organisation.
Identity and access management therefore needs to aggregate engagements from several sources. Each source owns its part – but organisation and manager always come from the same authoritative source.
Key takeaway: Many sources for engagements is fine, as long as all point to the same organisation tree.
3. Permissions
Applications define permissions to functions and information. Automatic assignment can use unit, engagement type, position, manager code, licence and process role – not position alone. The line manager confirms the need, the application owner approves access.
Permissions that cannot be derived from master data are handled in a manual process. All permissions need regular verification and removal when the engagement ends or changes.
- Create and maintain permission objects per application.
- Assign automatically where rules suffice, manually otherwise.
- Verify regularly and remove on exit.
Example
A new assistant nurse gets read access to the records system automatically via unit and position, while prescribing rights require a licence and are governed by another condition.
4. Process roles and budget
Process roles, such as application owner or approver, are attached to the employee and sometimes to the position – far from always. They are assignments, not titles.
The manager has their budget and the application has its own. The line manager approves need and cost, while the application owner decides who gets access.
Key takeaway: Separate who needs, who pays and who approves.