Documentation Index
Fetch the complete documentation index at: https://human-resource-docs.ha-consultancy.com/llms.txt
Use this file to discover all available pages before exploring further.
Permission set
The extension ships exactly one permission set:Human Resource HAC (object 70003100), declared in BC-Human-Resource-AL/src/permissionSet/PermissionSet.HumanResourceHAC.al.
It is Assignable = true so an administrator can assign it directly to users or include it in a higher-level permission set.
What it grants
| Object | Permissions |
|---|---|
| All HR-specific tables (70003101 – 70003160) | RIMD (read, insert, modify, delete) |
| All HR-specific table extensions | RIMD |
| All HR-specific pages | X (execute / open) |
| All HR-specific reports | X |
| All HR-specific codeunits | X |
| Standard BC tables (Employee, Gen. Journal Batch, Resource, etc.) | Not granted by this permission set. Combine with D365 BUS PREMIUM or one of the standard HR permission sets. |
BC-Human-Resource-AL/extensionsPermissionSet.xml, kept in sync for AppSource validation.
Recommended role bundles
| Role | Recommended permission sets |
|---|---|
| HR Administrator | Human Resource HAC + D365 BUS PREMIUM |
| HR Officer (limited) | A custom permission set derived from Human Resource HAC with RM (no insert/delete) on configuration tables, plus D365 BASIC |
| Employee self-service (mobile/portal app) | A dedicated low-privilege user that only has access to the published API codeunits. The HR.API uses client credentials OAuth — no per-employee user permissions are involved on the BC side. |
| AppSource auto-publish | Microsoft handles this — no manual permission set assignment needed in production. |
Adding the permission to a user
- Search for Users.
- Select the user → click Edit.
- On the Permission Sets FastTab, add
Human Resource HAC. - Confirm BC has applied it (the user’s effective permissions update on next session).
Field-level security
The extension does not define field-level permissions. Microsoft’sField-Level Security framework can be layered on top by an administrator using standard BC tools, targeting fields like bank account number or salary amount.
What is intentionally not granted
- Permission to delete companies — never something an HR user should do.
- Permission to change permission sets — same.
- Permission to modify the Permission Set HAC itself — to prevent privilege escalation, the permission set excludes itself from the modify rights.