Pay data should reach named roles with a stated reason: payroll to run it, finance to fund and account for it, the compensation owner to design bands, and each manager for their own reporting line only. Bulk reporting is the setting that matters most. When a leader asks for everything, ask which decision it serves.
Work from the decision backwards. Payroll administrators need individual figures because they process them. The compensation owner needs the full distribution because designing bands and running an increment cycle is impossible without it. Finance needs cost by unit and period to budget and account, which is a different shape of the same data. An HR business partner needs their supported population to advise on offers and increments. Line managers need their direct reports for the review they are asked to conduct. The employee needs their own. That is the complete list for most organisations, and everyone outside it - recruiters, administrators, IT, executive assistants, project leads - should be a deliberate exception with a name attached and a review date, not a default inherited from a job title.
Direct reports, in full, during the periods when they are making a decision. Beyond that the edges need drawing. Skip-level visibility is a genuine question: a director running an increment budget across three teams legitimately needs the whole tree, while a team lead does not. Peer figures are almost never justified, because a manager who can see what colleagues at their own level earn has been handed a grievance rather than a tool. Aggregates are the better answer for most planning: a manager needs the band, the position within it and the team cost, not necessarily a list of individual numbers year round. Consider time-boxing full visibility to the review window and reverting to aggregates afterwards, which also removes the awkward case of a manager retaining figures for a team they no longer lead.
These two are routinely lumped together and they want opposite shapes. Payroll works at the level of the individual: gross to net, statutory deductions, reimbursements, arrears and the bank instruction, because a payment is made to a person. Finance works at the level of the cost object: total cost by department, cost centre, project and period, plus accruals, provisions and variance against budget. Finance can do almost all of its work on aggregates and rarely needs a name attached to a figure outside a specific investigation. Designing the entitlements around that distinction shrinks the exposed population considerably, and it is worth checking how your [payroll processing](/payroll-management) supports it, since some systems only offer a full register and force finance into individual-level access to answer a departmental question.
Individual visibility is bounded by the effort of looking. Someone who can open one record at a time will not casually assemble a picture of the organisation. A report or extract that returns everybody in one action removes that boundary entirely, and the resulting file lives outside the system permanently. So treat the right to run an organisation-wide compensation report as a separate entitlement from the right to view a record, hold it with a small named group, and log each run with the requester and the purpose. Where a report is needed regularly, schedule it to a fixed recipient list in a controlled location rather than letting people generate ad hoc versions. If your [HR reporting](/hr-analytics-software) can serve the same question as a band distribution or a cost aggregate, use that instead of naming individuals.
Not with a flat refusal, which turns a design conversation into a power one. Ask which decision the data serves, then supply the smallest view that answers it. A chief executive asking about pay competitiveness needs band positioning and market comparison, not a list of names. A department head planning a restructure needs cost by team and role, not individual figures for people they do not manage. Someone investigating a specific concern needs specific records, granted for that purpose and reviewed afterwards. In the small number of cases where full visibility is genuinely the answer, grant it explicitly, record why, and log the access like any other. What you are avoiding is the standing grant with no stated purpose, because that is the entitlement nobody remembers to remove and nobody can justify when asked.
Two moments create pressure to widen access and both can be handled with less than people assume. During hiring, the recruiter needs the approved range for the role, the approver needs the proposed offer in the context of the band and the team, and neither needs the salaries of unrelated employees. Publishing the range to the recruiter rather than the underlying data solves it. During an increment cycle, managers need their own team, the compensation owner needs the whole picture to model and balance, and finance needs the aggregate cost of the proposal. The temptation is to build one spreadsheet with everything and circulate it for input, which hands the full distribution to every participant. A cycle run inside the [HR system](/hrms) with scoped views avoids that, and it also leaves a record of who proposed what.
Keep one short list: every person who can view compensation beyond their own team, and every person who can run a compensation report. That list should be small enough to read in a few minutes, and reviewing it once a year plus at every internal move is enough. Ask the owner of each entry to confirm it is still needed and record the answer. Check three specific leaks while you are there: reports scheduled to people who have changed roles, spreadsheets exported during the last cycle and never deleted, and access retained by managers whose teams have moved elsewhere. None of this requires tooling beyond what you already have, and doing it badly once a year beats designing an elaborate review that nobody completes.
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.
Free for 1 user · No credit card · Talk to a real hiring expert
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · Talk to sales · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
