Blog Product

Permissions that follow the organisation

6 min read

Who can see a salary looks like a list: these managers, those records. A list is accurate on the day it is written and starts to go wrong the first time someone moves. Following one invented duty manager through a transfer and a promotion shows why access to pay is a question about the shape of the organisation, and why it has to move when the organisation does.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes how access to pay data is structured; it states no statutory figure.

Why a list goes stale

In many organisations, access to pay data starts as a spreadsheet: a list of people and what each may see. Finance keeps it. HR updates it when it remembers. IT applies it to whatever system holds salaries.

The list is right on the day it is written. Then a supervisor moves to another department and keeps access to the team she left. A new manager joins and has no access to his own team for a month. A senior hire’s salary sits in a department where every manager can see it, because nobody thought to add an exception. None of this is anyone’s fault. A list records a decision once, and the organisation keeps changing after it.

The underlying problem is that the list holds access separately from the structure it depends on. Who a manager manages, and at what level, already lives in the employee record. A second copy of the same facts, kept by hand, will always lag.

Scoping as structure

TriblockHR scopes access from the organisation itself. There are seven roles, nine permission toggles and five layered scoping mechanisms. The scoping mechanisms decide which records a person can reach, based on where those records sit.

One of the five is employment level. It lets a senior record be withheld from a manager who is otherwise in scope for it. A department head’s salary does not become visible to the team leads in that department simply because they share it. The level sits on the record, and scoping reads it.

The effect is that access follows the organisation as recorded. The question “can this person see that record?” is answered from the structure.

One person, two moves

Take an invented duty manager, Corey Bethel, at a fictional resort, Pelican Sands. He starts in Food and Beverage, managing a team of servers and bartenders.

Before any move. Corey is a manager. He sees his team’s schedules, leave and attendance. He does not see their pay: managers never see salary in TriblockHR. His own pay is visible to the payroll and HR users whose scope includes him.

The transfer. Corey moves to Front Office as duty manager there, with effect from 1 June. Two questions follow. Whose records should he now reach? His new Front Office team, and no longer the Food and Beverage team. And who should now reach his? Front Office’s HR and payroll users, who may not be the ones who covered Food and Beverage.

The transfer itself is a dated event on his employment history. Scoping is by structure, so the question of who reaches whom is answered from where his record now sits. Whether a transfer re-scopes access with no further step from an administrator is something to confirm during implementation for your own configuration.

The promotion. In October, Corey is promoted to Rooms Division manager, a more senior employment level. Two things change. He is now senior to the duty managers below him, so their records sit within his scope for scheduling and leave. And his own record sits at a level that employment-level scoping can withhold from the duty managers who report to him. They do not reach his record just because he is now in their division.

Through both moves, Corey never sees anyone’s salary as a manager. That rule did not need updating.

Compare the spreadsheet. Each move needed someone to remember to remove one line and add another, in two directions, for him and for everyone whose access to him had changed. On a busy June, that is exactly the update that waits.

Rules that do not move

Some rules are fixed, and they apply whoever someone is and wherever they sit.

  • Managers never see salary. A manager’s role covers scheduling, leave and attendance for their team, and never pay.
  • Employees never see custom reports. Self-service is the same application under policy-scoped views, plus the mobile app, and it does not include the report builder.
  • A masked pay field is excluded from filters, sorts and grouping as well as from display, so a column cannot be inferred by sorting on it. The report builder page covers how masking works in reports.

Because these rules do not depend on a list, a move cannot leave one behind.

Who could see it, and who changed it

When a question arises about access to pay, it is usually in one of two forms. Who could see this salary in March? And who changed this salary, and when?

The second is answered by the audit history: about forty per-entity history tables holding the value before, the value after and the person who made each change, with an audit feed and downloadable reports of user activity.

The first is answered by structure and dates together. Corey’s employment history shows where he sat on any given day. Scoping reads where records sit. So the question of whose records he could reach in March depends on facts the record already holds by date.

Segregation of duties in an approval chain is a related question, covered on the financial services page.

Questions

Can managers see their team’s salaries in TriblockHR?

No. Managers never see salary.

How is a senior salary kept from managers in the same department?

Employment-level scoping lets a senior record be withheld from a manager who is otherwise in scope.

Why not keep a list of who can see what?

A list goes stale the first time someone moves. Scoping from the organisation’s structure reads facts the record already holds.

Can employees build reports?

No. Employees never see custom reports. Self-service is policy-scoped views and the mobile app.

Let access to pay follow the organisation, so a move never leaves a salary visible to the wrong person.

Book a demo

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