Permission Rules Reference
Use this page as a quick reference for how Janalix thinks about role-bound actions and sensitive record access.
This reference page is useful when you need a fast rule-level answer rather than a full task guide.
Who this is for
HR Admin, System Admin, Auditor
Estimated time
4 minutes
Category
Reference
Next best action
Open the workflow or role guide that comes immediately after this page.
Core principles
Permission rules in Janalix are designed to keep HR records private, auditable, and aligned to real work. If a permission cannot be explained in terms of responsibility, it is probably too broad.
- Viewing access should be intentional.
- Action rights should be tied to workflow ownership.
- Review-oriented roles should stay read-only whenever possible.
Common boundaries
Common boundaries include separating record creation from approval, separating operational work from audit review, and limiting archive retrieval to people who genuinely need retained records.
- Approvers should not need broad HR admin access.
- Employees should see only the requests or records relevant to them.
- Auditors should review history and evidence without normal editing tools.
When to review access
Review access when a person changes roles, when a workflow changes, or when an exception was granted temporarily and may no longer be needed.
Routine review is much safer than waiting for a permission problem to show up during an incident or audit.
Freshness and feedback
Keep this page current and useful
Use these details to judge whether the guide still looks current, and send a quick note if anything feels unclear, outdated, or incomplete.
- Last reviewed
- April 19, 2026
- Owner
- Janalix Team
Was this page helpful?
Send quick feedback so the docs stay practical for the next person.
Related guides
Keep moving with the next useful pages
Use related guides when you want a nearby task, a role-specific view, or a reference page that supports the workflow you just finished.