---
title: "Workday Role-Boundary Security Testing Matrix — Kiweely"
description: "Run a repeatable Workday Sandbox test matrix across Employee, Manager, and HR Partner personas using security analysis reports, Start Proxy, and API readback."
url: https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner
---

# How to Run Role-Boundary Security Tests Across Employee, Manager, and HR Partner Personas

Verify Workday security boundaries in Sandbox before rolling out reports, APIs, or external tools by combining four checks: View Security for Securable Item, Security Analysis for Securable Item and Account, Start Proxy UI checks, and user-delegated REST/WQL API readback.

-   **Checked** against Workday on November 15
-   Applies to **Workday Security & Testing**
-   7 min read
-   Published November 15
-   By Kiweely

To prove that regular employees, frontline managers, and HR Partners cannot read unauthorized peer compensation, disciplinary records, or out-of-scope organizations in Workday, run a four-step negative boundary test in Sandbox: inspect policies with **View Security for Securable Item**, trace cumulative user grants with **Security Analysis for Workday Account**, validate UI screens via **Start Proxy**, and execute live **REST / WQL / RaaS readbacks** under dedicated test accounts.

Most security leaks in Workday happen because teams only run *positive* tests—confirming a manager can see their own team—without running *negative* boundary checks against peer workers, indirect reports, and sensitive columns. Because Workday computes a user’s effective access as the **union of every security group they belong to**, one forgotten unconstrained group assignment silently widens both browser reports and external API responses.

## Step 1: Select Four Concrete Target Workers in Sandbox

Negative boundary testing requires fixed relationships between the **actor** (the persona signing in) and the **target** (the worker record being queried). Before running any report or query in Sandbox, pick four synthetic or non-production worker records and record their 32-character Workday IDs (`WID`) and `Employee ID` values:

1.  **Persona A — Regular Individual Contributor (`Employee As Self` only):** A non-manager employee in `Supervisory Organization` *Warehouse 4* with zero administrative or support roles.
2.  **Persona B — Peer Worker (Same Org):** Another individual contributor inside *Warehouse 4* reporting to the same manager as Persona A.
3.  **Persona C — Direct Manager (`Manager` Constrained):** The supervisory manager assigned to the `Manager` role on *Warehouse 4*, where *Warehouse 4* also has a child supervisory organization (*Warehouse 4 - Night Shift*) managed by a subordinate supervisor.
4.  **Persona D — Scoped `HR Partner` (`Role-Based Constrained` or `Intersection`):** An HR Partner assigned to support *Warehouse 4*, plus a fifth control worker in an unrelated supervisory organization (*Corporate Finance*) outside Persona D’s assigned scope.

Verify each test actor’s exact group memberships first by running **View Security Groups for User** in Sandbox. Confirm that neither Persona A nor Persona C holds stray unconstrained groups such as `HR Administrator`, `Payroll Administrator`, or `Implementers`.

## Step 2: Audit Securing Domains with Delivered Workday Reports

Before proxying or calling APIs, map which domains secure the sensitive fields and data sources in your test scope:

1.  Enter `View Security for Securable Item` (or search shortcut `secura`) in the Workday search bar.
2.  Check each high-risk item you plan to test—for example, `Total Base Pay - Amount`, `National Identifiers`, `Disciplinary Actions in Progress`, `Payment Elections Current`, and the `All Workers` data source.
3.  Click **View Security** on each match to list the securing domain security policy (such as `Worker Data: Compensation`, `Person Data: ID Information`, `Worker Data: Payroll (Payment Elections)`, or `Worker Data: Public Worker Reports`) and inspect both **Report/Task Permissions (`View` / `Modify`)** and **Integration Permissions (`Get` / `Put`)**.
4.  Run **Security Analysis for Securable Item and Account** for Persona A, Persona C, and Persona D against `Total Base Pay - Amount` and `National Identifiers`. This report pinpoints the exact security group and policy path if an actor holds unexpected access.
5.  Run **Security Analysis for Workday Account** (or **Compare Security of Two Worker Accounts** between Persona A and Persona B) to audit cumulative tenant permissions across functional areas.

Activate Pending Changes Before Testing

Whenever you tighten a domain or business process security policy during remediation, run **Domain Security Policies with Pending Changes** and execute **Activate Pending Security Policy Changes**. Policy edits do not apply to UI or API calls until activated.

## Step 3: Execute the Persona Role-Boundary Matrix

Every row in the matrix below defines an explicit actor, target record, data element, and expected Sandbox result. A **Pass** on a negative boundary means Workday omits the column, returns zero rows for the out-of-scope worker, or rejects the request with a permission error.

| Persona (Actor) | Target Worker Tested | Data / Action Requested | Expected Workday Result | Common Misconfiguration If Leaked |
| --- | --- | --- | --- | --- |
|  **Employee** (Persona A) | Self (Persona A) | Own time-off balance & payslips (`Self-Service: Time Off Balances`, `Self-Service: Payroll (My Payslips)`) |  **Allowed:** Returns Persona A’s own balances and payslips | Missing `Employee As Self` on self-service domain |
|  **Employee** (Persona A) | Peer in same org (Persona B) | Public directory info (`businessTitle`, `supervisoryOrganization`) |  **Allowed:** Returns public directory fields only | Normal if `All Employees` is on `Worker Data: Public Worker Reports` |
|  **Employee** (Persona A) | Peer in same org (Persona B) | `Total Base Pay - Amount`, `National Identifiers`, `Time Off Balances` |  **Blocked:** Empty/omitted fields or 403/400 error | Unconstrained group (`All Employees`) accidentally added to `Worker Data: Compensation` |
|  **Manager** (Persona C) | Direct report (Persona A) | Team time-off balances & job profile (`Worker Data: Time Off (Time Off Balances Manager View)`) |  **Allowed:** Returns direct report’s permitted team fields | Missing `Manager` group on manager view domain |
|  **Manager** (Persona C) | Direct report (Persona A) | Full `National Identifiers` (`Person Data: ID Information`) or bank account numbers |  **Blocked:** Omitted or masked per self-service constraint | `Manager` granted `View`/`Get` on `Person Data: ID Information` |
|  **Manager** (Persona C) | Indirect report in staffed child org | Compensation or review notes when policy requires direct reports only |  **Blocked** if group uses `COO` or `COUS`; **Allowed** only if `COAS` (`Management Chain`) is intended | `Management Chain` (`COAS`) used on policy instead of `Manager` (`COO`/`COUS`) |
|  **Manager** (Persona C) | Unrelated org (*Corporate Finance*) | Any non-public worker compensation or absence field |  **Blocked:** Zero rows returned for out-of-org target | `Manager (Unconstrained)` added to domain policy instead of constrained `Manager` |
|  **HR Partner** (Persona D) | Worker in assigned *Warehouse 4* | Staffing, compensation, and disciplinary status within *Warehouse 4* |  **Allowed:** Returns permitted HR fields for assigned org | Expected constrained `HR Partner` access |
|  **HR Partner** (Persona D) | Worker in *Corporate Finance* (unassigned org) | Compensation, disciplinary notes, or home contact details |  **Blocked:** Zero rows or omitted non-public fields | `HR Partner` assigned to an unconstrained group or top-level org role |

## Step 4: Verify Both Browser UI (`Start Proxy`) and Live API Readback

Testing only in the Workday browser UI misses integration-specific `Get` permissions and custom report sharing behavior. Run both halves of the check:

### Browser Verification via `Start Proxy`

1.  In Sandbox, run **Start Proxy** and enter Persona A.
2.  Search for Persona B, open Persona B’s worker profile, and confirm **Compensation**, **Pay**, **Personal -> IDs**, and **Performance / Disciplinary Actions** tabs are hidden.
3.  Run any shared custom reports (see [troubleshooting shared custom report empty rows and columns](https://kiweely.com/guides/workday-custom-report-sharing-security-empty)) to verify Persona A sees zero unauthorized columns.
4.  Repeat **Start Proxy** for Persona C (checking both a direct report in *Warehouse 4* and an indirect report in *Warehouse 4 - Night Shift*) and Persona D (checking *Corporate Finance*), then run **Stop Proxy**.

### Live WQL and REST API Readback

Workday disables external integrations and OAuth service connections during a `Start Proxy` session. To verify what external applications or AI assistants receive over the wire, sign in to Sandbox via an OAuth **API Client** (`Register API Client` with Authorization Code Grant and PKCE) using a non-production test user for each persona and run the exact same WQL query against `/wql/v1/data`:

Works

```
SELECT worker, employeeID, supervisoryOrganization, totalBasePay_Amount, nationalIdentifiers, disciplinaryActionsInProgress
FROM allWorkers
WHERE employeeID IN ('21097', '21402', '29811')
```

Inspect the HTTP status and JSON response for each persona’s Bearer credential:

-   When **Persona A (Employee)** runs this query including restricted fields (`nationalIdentifiers`, `disciplinaryActionsInProgress`), Workday’s WQL engine rejects inaccessible fields (`HTTP 400` *“Specify a valid report field”*) or, when querying only fields where Persona A has `Employee As Self` constrained access, populates `totalBasePay_Amount` **solely on Persona A’s own row** while leaving peer rows blank.
-   Repeat against REST endpoints such as `GET /common/v1/workers/{Persona_B_WID}/paySlips` and `GET /absenceManagement/v5/balances?worker={Persona_B_WID}` under Persona A’s session to confirm Workday denies cross-worker reads.

Works

```
GET /ccx/api/wql/v1/{tenant}/data?query=SELECT+worker,totalBasePay_Amount+FROM+allWorkers HTTP/1.1
Accept: application/json
```

## Automating Multi-Persona Boundary Checks

Running [multi-persona proxy tests](https://kiweely.com/guides/workday-multi-persona-proxy-testing) and [pre-AI security group audits](https://kiweely.com/guides/workday-security-audit-before-enabling-ai-agents) by hand takes hours whenever domain policies change. Teams connecting external assistants through [Kiweely Bridge](https://kiweely.com/bridge) (coming next) get an AI admin agent that automates role-boundary testing across Employee, Manager, and HR Partner personas in Sandbox and adds in-memory field redaction before publishing access to Production. Consultants and HRIS engineers configuring tenant security today can also run persona verification workflows directly in [Kiweely Vine](https://kiweely.com/vine).

## Watch Kiweely Vine build, secure and test an Extend app

![Kiweely Vine's Training Approval Extend app: the manager opens the employee's training request from his Workday tasks](https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner/media/vine-extend-app-training-approval-8f3cf9bc75d9.webp)

From the film: the manager opens the employee’s request in his Workday tasks.

From two short messages, Kiweely Vine builds a training approval app in a Workday Development tenant. It sets up the app’s access (Employee As Self and Manager) and the approval’s business process security policy, activates the pending security changes, adds the Manager step to the routing, then tests it as the employees and managers through Start Proxy, privacy checks included. 1 h 51 min from sign-up to the checked result.

[Watch the film (15 min)](https://www.youtube.com/watch?v=hoJV5tq90Ug) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Why isn't Start Proxy alone enough to test Workday API and external integration boundaries?

Workday proxy sessions run inside the interactive browser UI and explicitly block external service connections and integrations. To prove what an OAuth API client returns over REST, WQL, or RaaS, execute live API calls using non-production test accounts assigned to each target persona.

### Which Workday report shows the exact security group granting a worker unexpected access to a field?

Run Security Analysis for Securable Item and Account, enter the report field, task, or data source plus the worker's Workday account, and inspect every security policy and security group granting access.

### Why can a constrained Manager suddenly see compensation across the entire company?

Workday evaluates a user's effective permissions as the union of all their security groups. If that manager was also manually added to an unconstrained User-Based group (such as Report Writer or Compensation Administrator), the unconstrained group overrides the Manager constraint.

### Do edits to domain security policies take effect immediately during Sandbox testing?

No. Adding or removing security groups on a domain or business process security policy stays pending until an authorized administrator runs Activate Pending Security Policy Changes. Edits to security group membership or definitions take effect immediately.

## Sources checked

-   [Configurable Security Framework](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/configurable-security-framework.html)
-   [Choosing the Right Security Group Type (Security Reports)](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/choosing-the-right-security-group-type.html)
-   [Workday Tenants and Tools (Proxy Access)](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/workday-tenants-and-tools.html)
-   [Report Security (Troubleshooting Report Access)](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/report-security.html)

## Related guides

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

-   [### How to Audit Over-Permissive Workday Security Groups Before Turning On AI Agents Delegate AI agents inherit the union of an invoking user’s security groups, while ambient agents act through dedicated Ambient Agent Security Groups. Before activating any agent, audit unconstrained User-Based groups, stale role assignments, and View Security for Agent Skill pathways.](https://kiweely.com/guides/workday-security-audit-before-enabling-ai-agents)
-   [### Why does a shared Workday report show blank columns or fewer rows to another user? Because sharing a report does not override report security. Each user sees results based on their own access to the data source, the data source filter and every report field, so one report can show blanks, zeros or fewer rows.](https://kiweely.com/guides/workday-custom-report-sharing-security-empty)
-   [### Multi-Persona Testing in Workday: Verifying the Proxy Chain in Sandbox Step through the multi-persona proxy testing sequence in Workday Sandbox. Verify role handoffs, condition rule evaluation, and field writebacks across each approval tier.](https://kiweely.com/guides/workday-multi-persona-proxy-testing)
-   [### Constrained vs unconstrained security groups in Workday: which workers can a member see? An unconstrained group gives members access to every worker in the tenant for the secured item. A constrained group limits them to the organizations they are assigned to, such as an HR Partner for one supervisory organization.](https://kiweely.com/guides/workday-constrained-vs-unconstrained-security-groups)

### More guides on Business processes and security

[All 27 guides](https://kiweely.com/guides#business-processes)

-   [Aligning Workday Session Timeouts with External OAuth Access Token Lifetimes](https://kiweely.com/guides/workday-anonymous-vs-authenticated-session-timeout-oauth)
-   [How Workday Terminations and Job Transfers Affect Active OAuth Grants](https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers)
-   [Configuring Workday Pre-Hire Security So New Employees Can Complete Tasks Before Day One](https://kiweely.com/guides/workday-pre-hire-onboarding-access-before-day-one-security)
-   [Tuning Workday Business Process Notifications When Using External Mobile or Chat Approvals](https://kiweely.com/guides/workday-notification-delivery-settings-suppressing-duplicate-emails)
-   [Workday Time Off vs. Leave of Absence: Helping Employees Pick the Right Request Type](https://kiweely.com/guides/workday-leave-of-absence-vs-time-off-employee-request-routing)
-   [How to Trace Who Approves a Leave or Expense Request in a Workday Supervisory Org](https://kiweely.com/guides/workday-find-approver-chain-supervisory-org-business-process)
-   [Validating Country-Specific Address and Emergency Contact Formats in Workday Self-Service](https://kiweely.com/guides/workday-emergency-contact-home-address-change-validation-rules)
-   [How Workday Task Delegation Works When Managers Approve Through APIs](https://kiweely.com/guides/workday-delegation-rules-external-approvals-acting-on-behalf)

### From the blog on Business processes and security

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

-   [Why Workday Condition Rules Pass in Sandbox and Fail in Production](https://kiweely.com/blog/why-workday-condition-rules-fail-in-production)
-   [Why Copy-Pasting Workday Data into Consumer Chatbots Risks Client Data (and How Zero-Retention AI Fixes It)](https://kiweely.com/blog/workday-client-data-privacy-zero-retention-ai)
-   [Why Workday Business Processes Stall: The 5 Most Overlooked Routing Glitches](https://kiweely.com/blog/why-workday-business-processes-stall)

## 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.
