NobleCloak
Use cases

Salary data stays with the comp team

Author

Audrey

NobleCloak's AI Correspondent · AI-drafted, fact-checked against our sourced evidence before publishing.

Date Published

Salary data is one of the most sensitive things an HR system holds, and it is easy to expose by accident. A manager asks an assistant to help plan next year's team. An analyst asks for the average pay of a group. A new tool is connected to the HR system for a quite different reason. In each case, if the compensation tools are available to the assistant, salary data is one prompt away.

People teams are right to be cautious. The risk is not that the assistant is untrustworthy; it is that the question "who can see pay?" has an answer the team wrote down years ago, and an AI connection can quietly widen it.

The problem in HR's terms

The HR lead wants the existing rule to hold when AI enters the picture. If compensation tools are for the comp team and HR business partners, then they are for the comp team and HR business partners in every app, including the ones that did not exist when the rule was written.

Hiding the data inside each assistant is not workable, because there will be many assistants. The rule has to sit at the point where the assistants reach the HR system, and it has to be expressed in the roles the company already has.

The policy

Policy is written per tool: the action, who it applies to, and one of three decisions (allowed, needs approval, denied). Role-scoped policy decides which roles get a tool at all.

Action

Who

Decision

Read compensation data in the HR system

Comp team and HR business partners

Allowed

Read compensation data in the HR system

Every other role

Denied, and not listed

The compensation tools are entitled to two roles. For everyone else the tools are not offered, so the assistant does not just get an error. It has nothing to call. A manager's assistant can still help with planning questions that do not need pay, because the tools for those remain.

The entitlement is written in terms of roles the company already uses, so the rule reads the way the HR policy does.

Who handles it instead

Nobody approves anything here; the line is about who can see the tool. A manager who needs a pay figure asks the comp team or an HR business partner, as they always have. That keeps the people with the authority to share pay data in control of when it is shared.

If a team wants a path for occasional access, the tool for a specific role can be set to needs approval, which sends a request to a named approver or role in Slack or the web inbox. Many teams will prefer to keep the two-role entitlement simple.

What the Record of Decisions shows

Every decision goes into the Record of Decisions: who asked, which agent, which tool, the decision, who approved, and when. For compensation tools the entries answer two questions an HR lead is often asked.

  • Who has read compensation data through an AI assistant, and when? The answer is a list of comp team and business partner sessions, each with the agent and the tool.
  • Does the use match the work? The HR lead can look at the pattern, such as heavy use outside the merit cycle, and ask about it.

This is a straightforward audit of the people who are meant to have access.

Use it as the working record of policy decisions next to the HR system's own access logs.

What this does not do. It does not change what a permitted person can see inside the HR system, and it is not a substitute for the HR system's own permissions. It adds a rule at the AI connection so that widening the connection does not widen who can see pay.

Related scenarios

Get started and scope your HR tools by role.