---
title: "Fix Indirect-Report Leaks in Intersection Security — Kiweely"
description: "Prevent Workday managers and HR Partners from seeing unintended indirect reports by tuning COO, COUS, and COAS subordinate rules on Intersection Security…"
url: https://kiweely.com/guides/workday-security-groups-intersection-subordinate-org-visibility
---

# Preventing Accidental Indirect-Report Visibility in Workday Intersection Security Groups

Managers and HR Partners see unintended indirect reports in Workday for two reasons: setting component Role-Based Security Groups to Current Organization and All Subordinates (COAS) instead of COO/COUS, or leaving component groups on domain policies alongside an Intersection Security Group.

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

Accidental indirect-report visibility in Workday happens for two concrete reasons: configuring a component **Role-Based Security Group (Constrained)** with **Current Organization and All Subordinates (`COAS`)** instead of **Current Organization Only (`COO`)** or **Current Organization and Unassigned Subordinates (`COUS`)**, or forgetting to remove the standalone component security groups from domain policies after adding an **Intersection Security Group**.

Because Workday evaluates every custom report, REST endpoint, and WQL query as the **union** of all security groups permitted on the securing domain, a single leftover `Management Chain` (`COAS`) or standalone `HR Partner` permission overrides your narrowed intersection constraint and exposes every subordinate tier in the hierarchy.

## How Subordinate Organization Access Options Shape Visibility

Every **Role-Based Security Group (Constrained)** references a single assignable role (such as `Manager` or `HR Partner`) enabled for an organization type (such as `Supervisory` or `Location Hierarchy`). One assignable role can back **multiple** Role-Based Security Groups—each configured with a different **Access Rights to Organizations** setting:

| Organization Access Right | Workday Behavior on Child Organizations | Typical Delivered / Custom Group Pattern | Indirect-Report Visibility |
| --- | --- | --- | --- |
|  **Current Organization Only (`COO`)** | Grants access strictly to the organization node where the worker’s position holds the role assignment. | Strict direct-report `Manager (COO)` |  **None:** Never sees child supervisory orgs, even if a child manager seat is vacant. |
|  **Current Organization and Unassigned Subordinates (`COUS`)** | Grants access to the assigned organization plus child organizations **only where the role is unassigned**. Once a subordinate manager fills the child role, access stops at that boundary. | Standard `Manager` group |  **Conditional:** Sees child org workers only while the child org lacks its own role assignee. |
|  **Current Organization and All Subordinates (`COAS`)** | Grants access to the assigned organization and **every descendant organization** in the hierarchy regardless of whether child roles are staffed. | `Management Chain` or executive `HR Partner` |  **Full downward tree:** Sees all indirect reports across every subordinate level. |
|  **Current Organization and Subordinates to Level** | Grants access down a fixed integer number of subordinate levels from the assigned node. | Skip-level review groups (e.g., 1 level down) |  **Bounded:** Sees indirect reports down to *N* hierarchy tiers only. |

Check Multiple-Job Position Rules Too

On the same Role-Based Security Group definition screen, review **Access Rights to Multiple Job Workers** (*Role has access to the positions they support* vs. *Role for primary job has access to all positions* vs. *Role has access to all positions*). Selecting *Role has access to all positions* lets a secondary-job manager view compensation or position data tied to the worker’s primary job in another organization.

## How Intersection Security Groups Combine Subordinate Constraints

A single Role-Based Security Group can reference only one assignable role—and each assignable role should target one organization type (or paired hierarchy, such as `Cost Center` and `Cost Center Hierarchy`). When you need to restrict an HR Partner or regional leader along **two axes at once**—for example, *Supervisory Organization* **AND** *Location Hierarchy*, or *Supervisory Organization* **AND** a *Non-Hidden Staff* custom organization—you combine them inside an **Intersection Security Group** ([overview of Workday security group types](https://kiweely.com/guides/workday-role-based-user-based-intersection-security-groups)).

Workday evaluates an Intersection Security Group using two strict `AND` rules:

1.  **Membership intersection:** A worker is a member of the Intersection Security Group only if their position holds assignments satisfying **every** included security group (and they do not belong to an excluded unconstrained group).
2.  **Target constraint intersection:** A target worker record is visible only if that target satisfies the organizational constraints of **every** included security group simultaneously (and does not sit in an excluded target organization).

### Where Indirect-Report Leaks Creep Into Intersections

Suppose you intersect `HR Partner - Supervisory` with `HR Partner - Location Hierarchy (Canada)` so a regional partner only sees Canadian employees inside the *Sales* supervisory tree:

-   If `HR Partner - Supervisory` uses **`COAS`** and the partner is assigned at *Global Sales*, they see **every indirect report** across all sub-teams under *Global Sales* located in Canada.
-   If the business requirement was for that partner to see **only direct members of the top-level *Global Sales* leadership org** in Canada (excluding staffed regional sub-orgs), leaving `HR Partner - Supervisory` on `COAS` exposes hundreds of indirect reports. Switching that component group (or creating a dedicated component group on the same assignable role) to **`COO`** or **`COUS`** immediately trims subordinate org visibility.
-   Conversely, if an unassigned child supervisory organization exists under *Global Sales* and you used `COUS`, remember that Workday **role inheritance** flows down into unassigned child nodes—making workers in that unassigned child org visible until a subordinate assignee is placed on the child org (verify inherited vs. explicit assignments with the **Roles for Organization and Subordinates** report).

## Step-by-Step: Fixing Subordinate & Union Leaks on an Intersection Group

Follow these six steps in Sandbox to eliminate unintended indirect-report access across UI reports, RaaS, REST, and WQL:

### 1\. Audit Component Group Subordinate Rules

Run **View Security Group** on each Role-Based (Constrained) group included in your Intersection Security Group. Inspect **Access Rights to Organizations**:

-   Replace `COAS` with `COO` (strictly direct org) or `COUS` (direct org + unstaffed child orgs) if indirect reports in staffed child orgs should be hidden.
-   Do not edit a shared delivered group like `Management Chain` in place if business process routing depends on `COAS`; instead, create a dedicated Role-Based (Constrained) security group referencing the same assignable role with `COO` or `COUS` and include *that* group in your intersection.

### 2\. Verify Target Exclusion Rules (When Hiding Sensitive Sub-Orgs)

In the Intersection Security Group definition (`Create Security Group` -> **Intersection Security Group**), remember Workday’s structural rule: you can configure **either** an excluded unconstrained security group (member exclusion) **or** excluded target organizations in **Exclusion Criteria**, never both on the same group.

When using **Exclusion Criteria** to hide an executive or HR supervisory/custom organization, verify whether the exclusion is set to *Current Organization Only* or *Current Organization and All Subordinates*. Leaving a parent excluded org on *Current Organization Only* leaves child nodes exposed.

Remember that target exclusions apply only to **current positions** in the excluded organization and are meant for **View** policies, not business process step routing. For business process routing isolation, intersect with a **Custom Organization** role instead.

### 3\. Strip Component Groups from Domain Security Policies

This is the single most common bug in Workday intersection rollouts. Adding `ISG - HR Partner Scoped` to `Worker Data: Compensation by Organization` accomplishes nothing if `HR Partner` (unintersected) remains on that same domain policy ([see how constrained and unconstrained unions interact](https://kiweely.com/guides/workday-constrained-vs-unconstrained-security-groups)).

1.  Run **Action Summary for Security Group** on each component group (`HR Partner - Supervisory`, `HR Partner - Location`) to list every domain and business process policy where the component group still has standalone permissions.
2.  Use **Maintain Permissions for Security Group** to swap the component group out for your Intersection Security Group across target domain security policies.
3.  Run **Business Process Exception Audit** and **Security Exception Audit** immediately afterward to confirm removing the component group did not orphan a business process step or landing-page worklet.
4.  Run **Activate Pending Security Policy Changes** so your domain edits take effect (changes to security group definitions apply immediately, whereas policy permission edits wait for activation).

### 4\. Audit Unassigned Subordinate Orgs

If your component group uses `COUS`, run **Roles for Organization and Subordinates** and **Unassigned Organization Roles Audit**. Any child supervisory organization missing a `Manager` or `HR Partner` assignment will automatically roll up into the superior assignee’s `COUS` visibility scope.

### 5\. Account for Workday’s Native Intersection Limitations

Workday documents specific areas that assume whole-org access or ignore Intersection Security Group constraints—including `Move Workers`, `Create Position`, `Create Job Requisition`, `Compensation Review`, talent calibration, and certain compensation or report prompts. Always verify with a negative Sandbox readback test.

### 6\. Verify with WQL and Report Readback in Sandbox

Test in Sandbox via `Start Proxy` on [shared custom reports](https://kiweely.com/guides/workday-custom-report-sharing-security-empty), then via live WQL ([filtering organization hierarchies safely](https://kiweely.com/guides/wql-organization-hierarchy-filter-workersbyrole)) using a test user’s OAuth session:

Works

```
SELECT worker, employeeID, supervisoryOrganization, workersManager
FROM employeesByOrganization
WHERE supervisoryOrganization = 'eb39104c92a1100014f02918c721000a'
```

Run the query twice—once for the assigned parent `supervisoryOrganization` WID and once for a staffed child `supervisoryOrganization` WID:

-   Under **`COO`** (or **`COUS`** with a staffed child org), querying the staffed child org on non-public domains (`Worker Data: Compensation by Organization`, `Worker Data: Time Off (Time Off Balances Manager View)`) must return zero sensitive values.
-   If indirect-report figures still appear, run **Security Analysis for Securable Item and Account** on that report field and test user to spot the remaining security group in the union.

## Keeping Org Boundaries Tight Before Connecting External Tools

External portals and AI assistants using user-delegated Workday OAuth inherit the exact `COO`, `COUS`, `COAS`, and Intersection Security Group rules active in your tenant. Auditing those boundaries in Sandbox—manually with [Kiweely Vine](https://kiweely.com/vine) or through persona testing in [Kiweely Bridge](https://kiweely.com/bridge) and stateless employee screens in [Kiweely Leaf](https://kiweely.com/leaf) (both coming next)—keeps managers and HR Partners strictly inside their assigned scope.

## Frequently asked questions

### Why does a manager still see indirect reports after I added an Intersection Security Group?

Workday calculates effective access as the union of all security groups assigned to a domain policy. If you added your new Intersection Security Group to a domain policy without removing the standalone component Role-Based Security Group (such as Management Chain), the standalone group still grants broad subordinate visibility.

### What is the difference between Current Organization Only (COO) and Current Organization and Unassigned Subordinates (COUS)?

Current Organization Only (COO) restricts access strictly to the organization where the user's position holds the role assignment. Current Organization and Unassigned Subordinates (COUS) extends visibility into child supervisory organizations only when nobody is assigned to that role on the child organization.

### Can I nest an Intersection Security Group inside another Intersection Security Group?

No. Workday Intersection Security Groups cannot include other Intersection Security Groups, Rule-Based Security Groups, or Integration System Security Groups. They can include Role-Based, User-Based, Job-Based, Organization Membership, and Aggregation Security Groups.

### Do all Workday areas honor Intersection Security Group constraints?

No. Workday documents specific areas where entire-organization context is assumed or intersection limits apply—including Move Workers, Create Position, Create Job Requisition, Compensation Review, certain Employee Review/calibration flows, and some report prompts. Always verify with Security Analysis and proxy tests in Sandbox.

## Sources checked

-   [Role-Based Security (Access Rights to Organizations)](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/role-based-security.html)
-   [Intersection Security](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/intersection-security.html)
-   [Advanced Security Group Types](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-supplemental-for-administrators/advanced-security-group-types.html)
-   [Security Policy Configuration and Activation](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/security-policy-configuration-and-activation.html)

## Related guides

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

-   [### Filtering WQL Queries by Organization Hierarchy and workersByRole Without Throwing Security Errors To return workers in an HR Partner’s assigned organizations and subordinate hierarchies, use workersForHCMReporting with dataSourceFilter = workersByRole. Guard the endpoint with an exclude check so users without the constrained role do not trigger a hard WQL error.](https://kiweely.com/guides/wql-organization-hierarchy-filter-workersbyrole)
-   [### 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)
-   [### Workday Role-Based, User-Based, Intersection, and Aggregation Security Groups User-Based security groups grant unconstrained tenant-wide access to specific accounts, while Role-Based groups constrain access by organizational assignment. Intersection groups combine groups with AND logic to narrow access, and Aggregation groups combine groups with OR logic.](https://kiweely.com/guides/workday-role-based-user-based-intersection-security-groups)
-   [### 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 Reports and calculated fields

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

-   [How to Sum or Count Multi-Instance Rows in Workday Using Aggregate Related Instances (ARI)](https://kiweely.com/guides/workday-aggregate-related-instances-ari-sum-count)
-   [Blank vs. Empty in Workday Report Filters and Condition Rules: Why Your Filter Misses Rows](https://kiweely.com/guides/workday-blank-vs-empty-report-filter-prompts)
-   [How to Fix CellLimitExceededException: Exceeded Cell Limit in Workday Custom Reports and EIBs](https://kiweely.com/guides/workday-report-cell-limit-exceeded-exception)
-   [How to Build Multi-Condition Evaluate Expression Calculated Fields in Workday Without Hitting Nesting Limits](https://kiweely.com/guides/workday-evaluate-expression-nested-calculated-fields)
-   [How to Build a Workday Payroll Summary Report by Worker and Earning Code Over Any Date Range](https://kiweely.com/guides/workday-payroll-aggregate-earnings-deductions-report)
-   [How to Build an Extract Single Instance (ESI) Calculated Field in Workday (With Examples)](https://kiweely.com/guides/workday-extract-single-instance-calculated-field)
-   [Workday Date Calculated Fields: Increment or Decrement Date and Date Difference](https://kiweely.com/guides/workday-calculated-field-date-difference-increment)
-   [How do I group, aggregate and drill down in Workday advanced, matrix and composite reports?](https://kiweely.com/guides/workday-matrix-reports-aggregations-drilldowns)

### From the blog on Reports and calculated fields

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

-   [Approving Workday Expense Reports and Purchase Requisitions in Teams and Slack](https://kiweely.com/blog/workday-expense-report-and-requisition-approvals-in-teams-slack)
-   [Untangling a 14-Subreport Workday Composite Report Nobody on Your Team Built](https://kiweely.com/blog/reverse-engineering-inherited-workday-composite-reports)
-   [How Consultants Catch Silent Report and Browser Regressions After a Workday Semiannual Release](https://kiweely.com/blog/regression-testing-workday-ui-and-timezone-changes)

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