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:
- Create the account with Create Integration System User (and register an OAuth API client if using ISU and API client setup).
- 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 to pick the right boundary.
- 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:
- Run the View Security for Securable Item report from global search.
- 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, orWorker's Compensation Basis). - 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).
- 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 |
|---|---|---|
Integration Access PatternOutbound SOAP or REST read (Get_* operation) |
Policy Type to EditDomain Security Policy | Exact Permission Grid & Level RequiredIntegration Permissions -> Get |
Integration Access PatternInbound SOAP or REST write (Put_* / Import_* without BP) |
Policy Type to EditDomain Security Policy | Exact Permission Grid & Level RequiredIntegration Permissions -> Put (includes Get) |
| Integration Access PatternInbound web service that starts a Business Process | Policy Type to EditBusiness Process Security Policy + Domain Policy | Exact Permission Grid & Level RequiredInitiating Action (Web Service) on BPSP + Put on required data domains |
| Integration Access PatternIntegration triggered as a step inside a Business Process | Policy Type to EditBusiness Process Security Policy | Exact Permission Grid & Level RequiredWho Can Do Actions on Entire Business Process -> View All (to read event files/values) |
| Integration Access PatternCustom Report enabled as RaaS | Policy Type to EditReport Share settings + Domain Security Policies | Exact Permission Grid & Level RequiredAuthorized on report Share tab + Get / View on the RDS, RDS Filter, and every report/calculated field domain |
| Integration Access PatternLaunching or viewing integration events via API | Policy Type to EditDomain Security Policy (Integration functional area) | Exact Permission Grid & Level RequiredIntegration 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 (
Getvs.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 (
Viewvs.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 together:
- Open the Business Process Security Policy for that transaction (via Edit Business Process Security Policy).
- Locate the Initiating Action grid and find the specific
(Web Service)initiating action row. - Add your ISSG to that initiating action.
- 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.
# 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!# 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 timestampTenant-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:
- Run Domain Security Policies with Pending Changes and Business Process Security Policies with Pending Changes and confirm both return zero rows for your policies.
- 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.
- Execute a real API request (or Validate Only EIB run) using the ISU’s own credentials—and if the call fails before authorization with
401or WS-Security faults, troubleshoot Workday ISU authentication errors separately from domain policy permissions.
If you connect your tenant in Kiweely 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.