---
title: "Find Workday ISU Domain & Web Service Permissions — Kiweely"
description: "Use View Security for Securable Item, Domain Security Policies for Functional Area, and Activate Pending Security Policy Changes to grant exact ISU permissions."
url: https://kiweely.com/guides/workday-isu-permissions-activate-pending-security-policy-changes
---

# How to Find Every Domain and Web Service Permission an ISU Needs in Workday (Without Guesswork)

Stop guessing Workday ISU permissions: look up every web service operation, report field, and task in View Security for Securable Item, grant Get or Put access to your Integration System Security Group, and run Activate Pending Security Policy Changes.

-   **Checked** against Workday on November 13
-   Applies to **Workday Security**
-   6 min read
-   Published November 13
-   By Kiweely

To find every permission a Workday **Integration System User (ISU)** needs without trial and error, look up each web service operation, report data source, and report field in the **View Security for Securable Item** report, grant **Get** or **Put** (or **View**) access to your **Integration System Security Group (ISSG)** on each returned policy, and run **Activate Pending Security Policy Changes**. Never copy a broad administrator group or grant blanket functional areas just to silence a `Not Authorized` error.

Most integration permission failures come from one of three gaps: granting **View** instead of **Get**/**Put** on a domain policy, missing the **Business Process Security Policy** behind an inbound web service, or forgetting to activate pending security policy edits. Walking through Workday’s delivered security lookup reports resolves all three in a single pass.

## Step 1: Map the ISU to a Dedicated Integration System Security Group

Workday security policies never grant permissions directly to an individual **Integration System User** account. Permissions attach to an **Integration System Security Group (ISSG)**, and the ISU inherits access through that group:

1.  Create the account with **Create Integration System User** (and register an OAuth API client if using [ISU and API client setup](https://kiweely.com/guides/workday-integration-system-user-api-client)).
2.  Run **Create Security Group** and choose either **Integration System Security Group (Unconstrained)** for tenant-wide integration scope or **Integration System Security Group (Constrained)** when the integration must only access specific organizations. See [constrained vs. unconstrained security groups](https://kiweely.com/guides/workday-constrained-vs-unconstrained-security-groups) to pick the right boundary.
3.  Assign your ISU to the ISSG. Changes to security group definitions and ISU membership take effect immediately and do **not** require policy activation.

## Step 2: Look Up Exact Domains With `View Security for Securable Item`

Instead of guessing which domain controls `Get_Workers`, `Put_Applicant`, a REST resource, or a blank column on a RaaS custom report, ask Workday directly:

1.  Run the **View Security for Securable Item** report from global search.
2.  Enter the exact web service operation name, report data source, data source filter, or report field in the **Securable Item** prompt (for example, `Get Workers`, `Put Location`, or `Worker's Compensation Basis`).
3.  In the results, note three columns:
    -   **Functional Area** (for example, *Staffing*, *Core Compensation*, *Worker Data*, or *Integration*).
    -   **Domain Security Policy** or **Business Process Security Policy** securing that item.
    -   **Securable Item Type** and required permission level (**Get**, **Put**, **View**, **Modify**, or **View Get**).
4.  From the domain’s related actions menu, select **Domain > View Security Policy** to inspect all three item buckets secured by that domain (**Securable Actions**, **Securable Reporting Items**, and **Securable Integrations**) and verify the domain policy is enabled.

When you are scoping an integration across an entire module or checking whether a delivered domain policy ships disabled by default, run **Domain Security Policies for Functional Area** and select the target functional area (such as *Integration* or *System*).

| Integration Access Pattern | Policy Type to Edit | Exact Permission Grid & Level Required |
| --- | --- | --- |
|  **Outbound SOAP or REST read (`Get_*` operation)** | Domain Security Policy |  **Integration Permissions** -> **Get** |
|  **Inbound SOAP or REST write (`Put_*` / `Import_*` without BP)** | Domain Security Policy |  **Integration Permissions** -> **Put** (includes **Get**) |
|  **Inbound web service that starts a Business Process** | Business Process Security Policy + Domain Policy |  **Initiating Action** (Web Service) on BPSP + **Put** on required data domains |
|  **Integration triggered as a step inside a Business Process** | Business Process Security Policy |  **Who Can Do Actions on Entire Business Process** -> **View All** (to read event files/values) |
|  **Custom Report enabled as RaaS** | Report Share settings + Domain Security Policies | Authorized on report **Share** tab + **Get** / **View** on the RDS, RDS Filter, and every report/calculated field domain |
|  **Launching or viewing integration events via API** | Domain Security Policy (*Integration* functional area) |  **Integration Event** (**Modify** to launch, **View** to read events/output docs) + **Integration Process Event** BPSP |

## Step 3: Grant `Get`, `Put`, or `View` Without Over-Permissioning

Once you have your list of domains from **View Security for Securable Item**, open each domain’s related actions and select **Domain > Edit Security Policy Permissions**:

-   **Integration Permissions (`Get` vs. `Put`):** Add your ISSG here for Workday Web Services (SOAP), REST endpoints, and items marked **View Get**. Granting **Get** allows data extraction only. Granting **Put** allows both inbound writes and **Get** operations within that domain.
-   **Report/Task Permissions (`View` vs. `Modify`):** Add **View** only when a securable reporting item or custom report field explicitly requires Report/Task **View** rather than **View Get** (where **Modify** includes **View**).
-   **Calculated field dependencies:** If a RaaS report includes a five-layer calculated field chain, the ISSG needs domain access not just to the top-level field’s business object, but to every underlying source field referenced across the chain. Missing a single sub-field domain causes RaaS to return blank values without throwing an authentication error.

## Step 4: Check Business Process Security Policies for Inbound Operations

A classic trap occurs when an inbound EIB, Studio assembly, or Orchestration calls a web service like `Hire_Employee`, `Change_Job`, `Assign_Roles`, or `Request_Compensation_Change`. You grant **Put** on the domain, yet Workday still rejects the payload with a security error.

Inbound operations that trigger workflow events are governed by [domain vs. business process security policies](https://kiweely.com/guides/workday-domain-vs-business-process-security-policies) together:

1.  Open the **Business Process Security Policy** for that transaction (via **Edit Business Process Security Policy**).
2.  Locate the **Initiating Action** grid and find the specific `(Web Service)` initiating action row.
3.  Add your ISSG to that initiating action.
4.  If the integration runs *downstream* of an event—for example, a connector, Studio integration, or *Generate Documents* Run-As ISU reading data from an in-progress parent business process—add the ISSG to **View All** on the parent **Business Process Security Policy** as well.

## Step 5: Audit Staged Edits and Run `Activate Pending Security Policy Changes`

When you click **OK** on **Edit Domain Security Policy Permissions** or **Edit Business Process Security Policy**, Workday saves your edit in a **pending** state and continues evaluating live API calls against the previous security timestamp.

Fails

```
# Incomplete workflow:
1. Add ISSG_Payroll_Sync with Get permission on Domain: Worker Data: Current Staffing Information
2. Click OK -> Workday saves edit as Pending
3. Re-run RaaS / Get_Workers API call immediately -> Still returns blank fields or Not Authorized!
```

Works

```
# Complete change-control workflow:
1. Run "Domain Security Policies with Pending Changes" & "Business Process Security Policies with Pending Changes"
2. Confirm no unreviewed policy edits from other admins are sitting in the pending queue
3. Run "Activate Pending Security Policy Changes", enter a clear audit comment, and submit
4. Re-test API call -> Workday evaluates against the new active security timestamp
```

Tenant-wide activation and safe rollback

**Activate Pending Security Policy Changes** (secured in the *Security Activation* domain under *System*) activates **every** pending domain and business process policy edit in the tenant at once. Always check **Domain Security Policies with Pending Changes** and **Business Process Security Policies with Pending Changes** before submitting. If an activation introduces an unintended access change, run **View All Security Timestamps** and **Activate Previous Security Timestamp** to revert domain and business process policies back to a prior timestamp while you fix the pending configuration.

## How to Prove Your ISU Security Setup Is Complete

Before handing credentials to an integration developer or middleware team, verify three things in the tenant:

1.  Run **Domain Security Policies with Pending Changes** and **Business Process Security Policies with Pending Changes** and confirm both return zero rows for your policies.
2.  Open **View Security Group** for your ISSG and check its related actions (**Security Group > View Domain Permissions for Security Group**) to confirm every target domain and business process initiating action appears as active.
3.  Execute a real API request (or **Validate Only** EIB run) using the ISU’s own credentials—and if the call fails before authorization with `401` or WS-Security faults, troubleshoot [Workday ISU authentication errors](https://kiweely.com/guides/workday-isu-authentication-errors) separately from domain policy permissions.

If you connect your tenant in [Kiweely Vine](https://kiweely.com/vine), the agent can inspect a target custom report, EIB, Studio assembly, or web service list, trace every required securable item and calculated field dependency in your live tenant, check for pending unactivated policy edits, and present the exact least-privilege ISSG permission changes for your review before modifying anything.

## Frequently asked questions

### Why is my Workday ISU still getting permission errors after I added its security group to the domain?

Edits to Domain Security Policies and Business Process Security Policies remain in a pending state until an authorized administrator runs the Activate Pending Security Policy Changes task. Adding an ISU to an Integration System Security Group takes effect immediately, but policy permission changes never take effect until activated.

### What is the difference between Get and Put vs View and Modify permissions in Workday?

View and Modify control access to reports and UI tasks under Report and Task Permissions, where Modify includes View. Get and Put control access to web service operations and integration items under Integration Permissions, where Put includes Get. Items marked View Get allow groups with Get integration access to read View-secured reporting items.

### Why does an inbound Put or Submit web service fail even when the ISU has Put access on the domain?

Many inbound web services initiate a Workday business process such as Hire, Change Job, or Request Compensation Change. In addition to domain Put access, you must add the Integration System Security Group to the Initiating Action (Web Service) section on the corresponding Business Process Security Policy and activate pending changes.

### How can I check if another admin left unactivated security changes before I run Activate Pending Security Policy Changes?

Run the Domain Security Policies with Pending Changes and Business Process Security Policies with Pending Changes reports before activating. Because Activate Pending Security Policy Changes activates every pending policy edit across the tenant at once, always review those two reports first.

## Sources checked

-   [Steps: Grant Integration or External Endpoint Access to Workday](https://doc.workday.com/admin-guide/en-us/authentication-and-security/security-for-integrations/access-to-workday-data/dan1370797146076.html)
-   [Create Integration System Security Groups](https://doc.workday.com/admin-guide/en-us/authentication-and-security/configurable-security/security-groups/integration-security-groups/wvu1571267715376.html)
-   [Edit Domain Security Policies](https://doc.workday.com/admin-guide/en-us/authentication-and-security/configurable-security/security-policies/dan1370797389950.html)
-   [Edit Business Process Security Policies](https://doc.workday.com/admin-guide/en-us/authentication-and-security/configurable-security/security-policies/dan1370796362110.html)
-   [Activate Pending Security Policy Changes](https://doc.workday.com/admin-guide/en-us/authentication-and-security/configurable-security/security-change-control/dan1370796405018.html)

## Related guides

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

-   [### Workday Domain Security vs. Business Process Security Policies: Which Controls What A domain security policy controls View/Modify (and Get/Put) access to reports, report fields, setup tasks and web services. A business process security policy controls who can start, approve, cancel, rescind or view a transaction. Both need activation.](https://kiweely.com/guides/workday-domain-vs-business-process-security-policies)
-   [### 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)
-   [### Workday ISU or API client 401, invalid\_client, invalid\_grant These errors usually blame the token, but the real cause is the ISU’s own account, its security group’s activation, or the wrong client task — not a corrupted credential.](https://kiweely.com/guides/workday-isu-authentication-errors)
-   [### How do I set up an integration system user and API client in Workday so an external app can authenticate? Create the ISU, put it in an Integration System Security Group, grant domain permissions and activate them, register the client for integrations, then generate its refresh token and pick the ISU as the Workday account.](https://kiweely.com/guides/workday-integration-system-user-api-client)

### More guides on Integrations and APIs

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

-   [How to Fix The Load Contains a Duplicate Key and Invalid Reference ID Errors in Workday EIB](https://kiweely.com/guides/workday-eib-duplicate-key-reference-id-errors)
-   [How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors)
-   [Why Workday Scheduled Reports and Integrations Shifted Dates After Local Time Zone Processing](https://kiweely.com/guides/workday-local-time-zone-processing-report-integration-impacts)
-   [Workday Mass Job Change Tables vs. Change Job EIB: Limits, Security, and When to Use Each](https://kiweely.com/guides/workday-mass-job-change-vs-eib)
-   [Workday Data Cloud vs. EIB, RaaS, and Prism: Which Data Path Should You Use?](https://kiweely.com/guides/workday-data-cloud-vs-eib-raas-prism)
-   [How to change job profile and compensation in one Change Job SOAP request](https://kiweely.com/guides/workday-change-job-soap-profile-compensation)
-   [Why the Workday REST /workers endpoint leaves out terminated workers](https://kiweely.com/guides/workday-rest-api-workers-terminated)
-   [How to get the instance ID back after a POST to the Workday REST API](https://kiweely.com/guides/workday-rest-api-instance-id-after-post)

### From the blog on Integrations and APIs

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

-   [BYO API Keys on a Workday Consultant Laptop: Who Is the Controller?](https://kiweely.com/blog/byo-api-key-workday-consultant-laptop)
-   [Why Shared Integration System Users (ISUs) Are a Security Risk for Employee AI Chatbots](https://kiweely.com/blog/why-integration-system-users-are-dangerous-for-workday-ai)
-   [Mapping Microsoft Teams, Slack, DingTalk, and Lark Identities to Workday Worker OAuth](https://kiweely.com/blog/mapping-teams-slack-lark-sso-identities-to-workday-workers)

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