Hierarchy-Based Data Access for HR Software

Not everyone who uses ZeniaHR should see everyone. A branch HR executive needs the Pune staff, a department head needs the department, and a manager needs the people below them. Access Control gives each role a data scope: all, branch, department, hierarchy or self. Hierarchy means the user plus their full reporting line, taken from the reporting managers on record. Once enforcement is on, the scope narrows the employee list, attendance, overtime, analytics, reports and the HR dashboard.

How it works

The Company Head opens Access Control in Settings and selects a role.
Under data scope, pick All, Branch, Department, Hierarchy or Self for that role.
Branch uses the user's own branch, and Department uses the department linked on the user's own employee record.
Hierarchy covers the user plus everyone below them in the reporting line, direct and indirect.
With enforcement switched on, the scope applies to the employee list, attendance punches, overtime, attendance analytics, reports and the HR dashboard.
The Company Head and Super Admin are never narrowed.

What you can set

All: every employee of the company.
Branch: employees of the user's own branch.
Department: employees of the user's own department.
Hierarchy: the user and their whole reporting line.
Self: the user's own records only.
Scopes apply only after the company's enforcement switch is turned on.
Field masking for salary, bank and contact is set on the same role.

Why scope matters

Salary sheets, attendance penalties and exit reasons are sensitive, and in a multi-branch company the default of everyone sees everything causes real problems. A branch accountant who can read head office salaries, or a supervisor who can see another team's absences, creates gossip and grievances. Scoping each role to the data it needs keeps the system useful for managers without turning it into a noticeboard for private information.

Worked example: an NBFC with 12 branches

A Jaipur-based NBFC has 12 branches and 340 staff. The Branch Manager role gets Branch scope, so the Ajmer branch manager sees the 22 Ajmer employees on the list, the live attendance board and the reports. The Collections Head gets Hierarchy scope, because his 41 people sit in four branches but all report up to him. Regional HR executives use the HR role with All scope, and staff use the Employee role with Self. Salary is hidden for the Branch Manager and Collections roles, so both work with attendance and leave without seeing pay.

Before switching on enforcement

Scopes depend on clean data, so prepare it first. A scope built on a wrong branch or a missing reporting manager shows a user too little or too much, and both mistakes are noticed on the first morning after enforcement goes on.

Link every employee to the department master, since Department scope matches linked departments, not typed text.
Set reporting managers for everyone, or Hierarchy scope will show too few people.
Review each role's scope and masking together.
Switch on at a quiet time, and switch off to fall back to the older permission matrix if something looks wrong.

See data access by hierarchy in a demo

We show it on a video call with your own shifts, leave types and rules. Free for your first 50 employees.

Book a free demo See pricing

Frequently asked questions

What is hierarchy-based access in HR software?

It limits what a user sees to themselves and the people who report to them, directly or through other managers. In ZeniaHR the Hierarchy data scope follows the reporting manager on each record, so a plant head sees every supervisor and operator below them, and a line supervisor sees only their own crew.

Can a department head see only their own department?

Yes. Give their role the Department scope in Access Control. Once enforcement is on, the user sees employees linked to the same department as their own employee record, across the employee list, attendance, overtime, analytics, reports and the dashboard, and nobody from other departments.

Does data scope also hide salaries?

No. Data scope decides which employees a role can see. Field masking decides which details of those employees are shown, with salary, bank and contact each set to full, masked or hidden. Most companies use both: a scope for the rows and masking for pay and bank details.

Who can change data scopes?

Only the Company Head, from Access Control in Settings. Scopes take effect when the company's enforcement switch is on, and until then the older per-user permission matrix decides access. The Company Head and Super Admin always see all data, whatever the scopes say.