Roles & Access Model
The IR roles
| Role | Intended for |
|---|---|
| HR Manager | Senior HR/IR users: the broadest operational access, including IR Role Restrictions, the appeal Actions menu and the HR Exception Report. This replaces the former IR Manager role. |
| IR Officer | IR practitioners who create and manage cases within the scope they're permitted. |
| IR User | Restricted, mainly read-oriented access. On case and outcome documents, and on Contract of Employment, an IR User sees submitted records only, apart from cases where they are the Responsible IR. |
When a user holds more than one of these, the highest role wins (HR Manager, then IR Officer, then IR User) for every restriction check. Roles can't be combined for a wider or narrower scope.
IR Manager has been retired. Everything the IR Manager role used to do, including its row on IR Role Restrictions, now belongs to HR Manager. Existing IR Manager users should be given HR Manager.
Other roles
| Role | Purpose |
|---|---|
| Training Manager / Training Administrator / Training Facilitator | Management, administration and facilitation of training and inductions, including the Training Compliance Dashboard. |
| Anonymous Report Investigator | The only role that receives Anonymous Report notifications. See Anonymous Report. |
| HR User, Payroll Manager / Payroll User, Accounts Manager / User | Standard HRMS/ERPNext roles used by the SA payroll, VAT and labour workspaces. |
System Manager has full administrative access, runs ZA Local Setup, and is the only role that can directly cancel a submitted Disciplinary Action, Incapacity Proceedings, Poor Performance or Appeal Against Outcome. Everyone else must use a formal Appeal.
How access is decided
Holding an IR role establishes which restriction bucket applies. The actual scope comes from IR Role Restrictions, plus three rules that apply on top:
- Own-case exclusion. Nobody can open a Disciplinary Action, Incapacity Proceedings or Poor Performance case about their own Employee record through general IR access, not even its Responsible IR.
- Responsible IR override. The user named as Responsible IR on a case can always see that case and every document that follows from it (NTA Enquiry, Written Outcome, sanctions, appeal), even if their Designation or Branch Limits would otherwise hide it.
- Complainant access. The complainant's user account is automatically given read-only access to the case they raised (a document share), and nothing else.
Restrictions are enforced the same way everywhere:
- Lists and reports. Restricted records are filtered out of queries.
- Direct access. Opening a record by URL is blocked, not just hidden.
- Notification emails. Weekly digests and creation alerts are narrowed per recipient, so nobody receives in an email what they couldn't open in the app.
In this example, an IR Officer whose Branch Limits cover only Demo Site North still sees a case at Demo Site South, because she is its Responsible IR:

Next: IR Role Restrictions.