Understand Roles And Permissions
See how Janalix separates responsibilities so sensitive HR records stay controlled and auditable.
Janalix is designed around clear role boundaries. Permissions are not only a convenience setting; they are part of the product's control model for employee records.
Who this is for
HR Admin, Approver, Employee, Auditor, System Admin
Estimated time
5 minutes
Category
Start Here
Next best action
Open the workflow or role guide that comes immediately after this page.
Role model
Janalix uses clear role boundaries so sensitive employee records remain private, auditable, and easy to reason about.
- HR Admins run operational workflows and manage most day-to-day records.
- Approvers make assigned decisions without owning the broader admin surface.
- Employees complete focused tasks like signatures, acknowledgements, and uploads.
- Auditors and reviewers inspect evidence without normal editing access.
Use the shortest role model that still matches reality
When a user can do their job without extra visibility, the workflow stays easier to govern and explain.
Operational owner
HR Admin
Owns record setup, workflow routing, and most day-to-day document handling.
Decision maker
Approver
Reviews assigned records and takes decision actions without broad admin access.
Task participant
Employee
Completes focused requests like signatures, acknowledgements, and uploads.
Read-only reviewer
Auditor
Reviews evidence, history, and retained records without normal editing rights.
Real product screenshot
Role boundaries are easiest to understand when the current scope is visible
- 1
The active workspace matters as much as the role
Users need to know which organization boundary they are operating inside before any permission conversation makes sense.
- 2
Role badges should reinforce the user's real job
People should be able to look at the current scope and immediately understand whether they are acting as admin, approver, or reviewer.
- 3
The visible actions should stay consistent with those badges
When the action set and the role labels drift apart, users quickly stop trusting the access model.
How to think about access
Access should follow responsibility. If a person does not need to see or change a record to do their job, that access should usually stay off.
A good permission setup answers three questions quickly: who can view the record, who can act on it, and who can review its history later.
When to open reference pages
Open role and permission reference pages when you need a rule-level answer, such as whether a user should approve, archive, retrieve, or review a record.
- Use quick starts for onboarding.
- Use workflow guides for task completion.
- Use permission reference pages when you need a policy answer fast.
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.
HR Admin Quick Start
Learn the shortest path from setup to running controlled employee document workflows as an HR Admin.
Permission Rules Reference
Use this page as a quick reference for how Janalix thinks about role-bound actions and sensitive record access.
Manage Access And Role Assignments
Keep Janalix access aligned to real responsibilities so records stay private, controlled, and reviewable.