Blog Industry

Scoping access by role

5 min read

In a public body, the question of who should see what is already answered by the establishment: who sits in which division, at which grade. An HR system that scopes access by that structure follows the organisation, and an administrator re-points it when the organisation changes. One invented ministry, mapped person by person, and then two people moved, shows how.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes access scoping in TriblockHR; it states no public-service rule.

The access question is the establishment

Take an invented ministry, the Ministry of Coastal Affairs, with about 400 staff. Its structure: a permanent secretary’s office; three divisions (Fisheries, Ports and Coastal Planning); and grade bands from clerical, through officer, to senior officer.

Who should see whose record is already written in that structure. The Fisheries director should see Fisheries staff. A clerical officer in Ports should see nothing about anyone else. The permanent secretary’s office should see everything, but even there, a junior HR clerk should not see senior officers’ pay.

An access model that follows the establishment does not need a separate list of who can see whom. It reads the structure.

Seven roles, mapped to offices

TriblockHR has seven roles: administrator, HR administrator, HR clerk, payroll administrator, payroll clerk, employee, and no access. Core HR covers them.

The ministry maps them:

  • Administrator: two officers in the permanent secretary’s office, who manage the system itself.
  • HR administrator: the ministry’s HR manager.
  • HR clerk: three HR officers, who maintain records day to day.
  • Payroll administrator: the payroll manager, who approves runs.
  • Payroll clerk: two payroll officers, who prepare them.
  • Employee: everyone else, for self-service.
  • No access: people who are on the establishment but should reach nothing in the system, such as a seconded officer whose record the ministry holds but who works elsewhere, or a leaver.

No access is a role in its own right. An account can exist, a person can be on the establishment, and the account can reach nothing. That is a defined state.

Scope by division and grade band

A role says what someone can do. Scope says to whom.

Alongside the roles, TriblockHR has nine permission toggles and five layered scoping mechanisms. One of them is employment level, so a grade band scopes too. The combination means a divisional officer can see a division and a grade band only.

At the ministry:

  • the Fisheries director, as a manager, sees Fisheries staff for scheduling, leave and attendance;
  • an HR clerk assigned to Ports reaches Ports records, up to the officer band;
  • senior officers’ records in Ports are withheld from that clerk by employment-level scope, even though they are in Ports, because the clerk’s scope does not reach the senior band.

A senior record can be withheld from someone who is otherwise in scope for its division. That is what makes the grade band useful: division alone would show the clerk every Ports record, senior or not.

Pay, masking and the closed employee route

Managers never see salary. The Fisheries director can schedule her staff and approve their leave. She cannot see their pay.

Masking. Where a report includes a pay column a user may not see, the column is masked, and a masked column is refused as a filter, a sort key, a grouping and a total. So a hidden figure cannot be inferred by sorting on it, filtering above a threshold or totalling a small group. The report builder page covers masking.

The employee route is closed. The employee role is never granted a report route: report building, report viewing, the audit log and analytics are closed to it. That is structural, so it cannot be switched on by mistake.

Two people move

A transferred employee. A fisheries inspector, Nadine, transfers to Ports. In TriblockHR, employment history is held by effective date, and a transfer is a dated event on her record. Filters hang off current employment, so from the date of the transfer Nadine’s record reads under Ports. The Ports director now sees her for scheduling and leave; the Fisheries director no longer does. Her earlier history stays on her record.

A promoted officer. A divisional HR officer, Clive, who has been the HR clerk for Fisheries, is promoted to a senior HR post covering Ports. His own record moves to Ports. But his access as a user, the scope he works within, is a separate setting from where his record sits.

Re-pointing Clive’s scope is an administrator’s step: remove Fisheries from his scope, add Ports and the bands his new post covers. The ministry should treat it as part of the promotion, done on the same date, by an administrator, and recorded. Until it is done, Clive’s access reflects his old post.

The same applies in reverse when someone moves down or out of a role: an HR clerk who becomes a project officer with no HR duties should leave the HR clerk role on the same date. An access model that follows structure only works if the structure on the record and the access on the account move together.

That step is easy to miss, because Clive’s record has moved and it looks finished. A promotion checklist that includes “re-point scope” catches it. The access review the ministry keeps on its own file is the second check; an audit asks what changed, and who could have changed it covers that review.

Questions

What roles does TriblockHR have?

Administrator, HR administrator, HR clerk, payroll administrator, payroll clerk, employee and no access.

Can a senior record be hidden from someone in the same division?

Yes. Employment-level scope lets a grade band withhold a senior record from someone otherwise in scope.

Can employees run reports?

No. The employee role is never granted a report route.

What happens to access when an officer is promoted to another division?

Their record moves on the dated event. Their own scope is re-pointed by an administrator as part of the promotion.

Scope access by the establishment, and re-point it whenever someone moves.

Book a demo

  • SOC 2 Type II attested
  • AES-256 at rest
  • 99.9% uptime
  • Built in The Bahamas