---
title: "Compensation Statement Screens and Peer Pay Redaction"
description: "How Workday's constrained compensation security keeps peer pay off a manager statement screen."
url: https://kiweely.com/guides/compensation-statement-field-redaction-manager-peers
---

# Compensation Statement Screens and Peer Pay Redaction

Managers see compensation review statements for direct reports through Worker Data: Compensation Review Statements on a constrained role. A statement screen should render only the fields that call returns. Filling gaps with a broader account shows peer pay.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   4 min read
-   Published November 16
-   By Kiweely

A manager statement screen fails when a peer’s salary appears, even for a moment, even in a tooltip. Workday already has the control that prevents that: constrained security on compensation domains. The screen’s job is to show the response and stop. Hiding a field in CSS after a broader account fetched it is not redaction.

[Kiweely Leaf](https://kiweely.com/leaf) (coming next) calls Workday as the signed-in person and stores no compensation data. That design only holds if the screen never swaps in another account to “complete” the page.

## The domains Workday names for statements

[Prepare for compensation reviews](https://doc.workday.com/admin-guide/en-us/human-capital-management/compensation/set-up-compensation-reviews/ylg1489603549601.html) separates two domains in Advanced Compensation:

-   **Self-Service: Compensation Review Statements**, so employees can print their own statements.
-   **Worker Data: Compensation Review Statements**, so managers can print statements for their direct reports.

Other domains on that page are easy to over-grant. **Process: Compensation Review Process Participant** lets a planner view or plan subordinate supervisory organizations and needs Modify to plan awards. **Process: Compensation Review Process Reviewer** lets HR partners and location or regional managers view or edit awards for assigned employees. A statement screen for a frontline manager should use the statement domain scoped to direct reports, not a reviewer domain aimed at a region.

[Role-based constrained groups](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-supplemental-for-administrators/advanced-security-group-types.html) are how Manager and HR Partner stay inside the organizations where the role is assigned. Membership follows the role on the position. Target access is those organizations. The same course manual lists **role-based unconstrained** groups, whose target access is not limited to those organizations. An unconstrained Manager group on a compensation domain is how peer pay leaks. Employee as Self is a self-service group constrained to the worker’s own data, which is the right group for “my statement.”

Workday’s [security course](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/security-group-configuration-and-constraints.html) uses the same picture: a manager sits in the Manager role-based constrained group and in Employee as Self, and a compensation administrator is a different membership. The screen should not collapse those into one fetch.

## What “redaction” means on a pass-through screen

| Situation | What the worker should see |
| --- | --- |
| Employee opens their statement | Fields returned under Self-Service: Compensation Review Statements |
| Manager opens a direct report | Fields returned under Worker Data: Compensation Review Statements for that organization |
| Manager opens a peer | No row. Workday omitted them. |
| A field is absent on a direct report | Leave it blank. Do not re-query as Compensation Administrator. |
| The UI hides a value that the response included | You still transmitted peer or out-of-scope pay to the browser. Fix the domain, then the screen. |

[Segmented security for compensation plans](https://doc.workday.com/admin-guide/en-us/human-capital-management/compensation/manage-compensation/dan1370796725725.html) is a separate, heavier setup for dividing compensation *setup* data, such as plans, among compensation partners by country or similar segments. Workday says intersection security, constrained job-based security groups, and rule-based security groups are not supported for Compensation. Do not plan peer redaction on those group types and expect it to apply to compensation data.

Segment-based groups also do not replace the manager’s organization constraint. A segment can limit which plan definitions a compensation partner maintains. It does not, by itself, mean a manager of one team can open another team’s statements.

## How to test the screen

Sign in as three people Workday already distinguishes: the employee, their manager, and a manager of a sibling team. Print or open the statement in Workday first, under **Start Proxy** if that is how you test personas, and write down which fields appear. The Leaf screen, when you connect it, should match that list person for person.

[Leaf](https://kiweely.com/leaf) (coming next) publishes the layout only when you say so. The domains stay in your tenant. If a statement design needs a field the manager’s domain does not include, change the domain in a non-production tenant and look at who else gained access before you widen production.

## Questions

### Can the screen compute a total the payload left out?

Only from numbers present in that response. Adding a peer average, a range built from other workers, or a “team compa-ratio” fetched under a compensation partner account is a new disclosure. If leadership wants that figure, it belongs on a report secured to the people who should see it, and the screen runs as one of those people.

### Is this the same as compensation review planning?

No. Planning awards uses the process participant and reviewer domains and can modify awards. A statement screen is a read of the statement the person is allowed to print. Keep the write off the page unless you have deliberately enabled the planning step for that role.

## Sources checked

-   [Steps: Prepare for Compensation Reviews](https://doc.workday.com/admin-guide/en-us/human-capital-management/compensation/set-up-compensation-reviews/ylg1489603549601.html)
-   [Role-based constrained security groups](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-supplemental-for-administrators/advanced-security-group-types.html)
-   [Set Up Segmented Security by Compensation Plans](https://doc.workday.com/admin-guide/en-us/human-capital-management/compensation/manage-compensation/dan1370796725725.html)
-   [Security group configuration and constraints](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/security-group-configuration-and-constraints.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Performance Check-In and Goals Screens Managers Will Open Workday documents check-ins on Staffing, goal reads and anytime feedback on Performance Enablement v4, and goal edits on the Manage Goals business process. A manager screen should use those resources and leave formal reviews in Workday when the API listing has no review write.](https://kiweely.com/guides/performance-check-in-goals-screens-managers-open)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [Publishing One Employee Screen to Web, Teams, and Phone](https://kiweely.com/guides/one-screen-definition-web-teams-phone)
-   [Coexisting with Workday Time Kiosk: Punch versus the Personal Phone](https://kiweely.com/guides/coexist-workday-time-kiosk-punch-versus-phone)
-   [What should happen to a manager’s supervisory organization while the manager is on leave in Workday?](https://kiweely.com/guides/workday-manager-on-leave-supervisory-organization-interim-manager)
-   [Why are Change Organization Assignments fields blank after a Change Job that changes the position?](https://kiweely.com/guides/workday-change-job-organization-assignments-blank)
-   [Test Workday as Employee, Manager, and Admin with Start Proxy](https://kiweely.com/guides/test-workday-with-start-proxy-personas)
-   [Workday Preferred Display Language vs Preferred Locale: what each one changes, and why self-service items disappear](https://kiweely.com/guides/workday-manage-user-language-locale-translations-self-service)
-   [How Workday Calculates Projected Time-Off Balances as of a Future Date](https://kiweely.com/guides/workday-accrued-time-off-balance-as-of-future-date)
-   [Resolving SSO Redirect Loops on the Workday OAuth Authorize Endpoint](https://kiweely.com/guides/workday-sso-saml-oidc-loop-external-oauth-authorize-endpoint)

### From the blog on More Workday guides

[All posts](https://kiweely.com/blog)

-   [Who Can Publish an Employee Screen, and Who Can Only Request One](https://kiweely.com/blog/who-can-publish-leaf-apps-versus-request)
-   [Offline Frontline Screens: What a Pass-Through Can Promise](https://kiweely.com/blog/offline-poor-connectivity-frontline-pass-through)
-   [Deep Links and QR Codes into the Right Employee App](https://kiweely.com/blog/deep-links-qr-codes-employee-workday-screens)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
