---
title: "Call Workday RaaS Reports with User-Delegated OAuth"
description: "Call web-service-enabled Workday custom reports (RaaS) using OAuth 2.0 Bearer credentials so row-level and field-level report security runs as each employee."
url: https://kiweely.com/guides/workday-raas-user-delegated-oauth-vs-isu-basic-auth
---

# Calling Workday RaaS Reports with User-Delegated OAuth Instead of an ISU

Replace shared Integration System User Basic authentication on Workday Reports as a Service (RaaS) with user-delegated OAuth 2.0 Bearer credentials so custom reports automatically enforce each signed-in worker’s row-level and field-level security.

-   **Checked** against Workday on November 15
-   Applies to **Workday Reporting & RaaS**
-   5 min read
-   Published November 15
-   By Kiweely

Web-service-enabled custom reports in Workday—known as **Reports as a Service (RaaS)**—accept standard `Authorization: Bearer` headers issued by a user-delegated OAuth 2.0 API client. Switching RaaS calls from HTTP Basic authentication on a shared Integration System User (ISU) to user-delegated OAuth lets one custom report safely serve employees, managers, and HR partners while Workday enforces row-level and column-level security per caller.

## ISU Basic Auth vs. User-Delegated OAuth on RaaS

Historically, teams wired external dashboards and portals to Workday RaaS endpoints using an ISU username and password over HTTP Basic auth. When humans sit behind those queries, ISU Basic auth creates severe security and maintenance debt:

| Security & Ops Dimension | ISU with HTTP Basic Auth | User-Delegated OAuth 2.0 (`Bearer`) |
| --- | --- | --- |
|  **Client Registration** | `Create Integration System User` (often no API client) | `Register API Client` (Authorization Code Grant + PKCE) |
|  **Row-Level Population** | Unconstrained ISSG sees **all** workers across the company unless custom prompt filters work flawlessly | Constrained by caller’s own security groups (`Manager` sees own supervisory org; `Employee As Self` sees self) |
|  **Column / Field Redaction** | Returns every column granted to the privileged ISU (e.g., Base Pay, Bonus Target) | Automatically omits fields secured to domains the signed-in caller lacks `View` permission on |
|  **MFA & Corporate SSO** | Bypasses SSO/MFA via static password | Enforces SAML SSO, OIDC, and MFA on interactive login |
|  **Audit Attribution** |  **View User Activity** logs every report download under one shared ISU |  **View User Activity** logs the exact worker `System Account` who ran the report |
|  **Credential Exposure Risk** | Single static password exposes full unconstrained report extract | Short-lived, user-scoped Bearer credential; zero shared password |

## How RaaS Evaluates Security Under a User-Delegated Bearer Credential

A common misconception among Workday developers is that the `<owner>` path segment inside a RaaS URL runs the report “as” the report owner. It does not.

Consider a RaaS JSON URL obtained via **Related Actions > Web Service > View URLs** on a custom report:

text

```
https://<services-host>/ccx/service/customreport2/<tenant>/<report_owner>/<Report_Name>?format=json
```

In that URL, `<report_owner>` (for example, `lmcneil`) is purely a **naming qualifier** identifying which user owns the custom report definition (alongside its immutable `urn:com.workday.report/Report_Name` namespace). When Workday receives an HTTP `GET` request carrying `Authorization: Bearer <access_credential>`, Workday evaluates four checks against the **authenticated OAuth caller**:

1.  **API Client Functional Area Scope:** Does the API client include the Functional Areas of the report’s data source and fields, plus **Include Workday Owned Scope**? ([Scoping guide](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping))
2.  **Report Sharing (`Share` tab):** Is the custom report shared with a security group the signed-in caller belongs to (or shared with authorized data-source users)?
3.  **Data Source & Filter Security:** Does the caller hold `View` permission (under **Report/Task Permissions**) on the domain securing the report’s Data Source and Data Source Filter?
4.  **Contextual Row & Column Security:** Which target instances (workers, positions, organizations) do the caller’s constrained or unconstrained security groups cover, and which column domains can they view?

## Step-by-Step Setup: User-Delegated RaaS Execution

### 1\. Copy and Prepare the Custom Report

Never enable a Workday-delivered standard report directly as a web service, as twice-yearly Workday releases can alter standard report columns and break downstream JSON parsers.

1.  Run **Copy Standard Report to Custom Report** (or **Create Custom Report** for a new Advanced report).
2.  Confirm the **Report Owner** username does **not** contain a backslash (`\`) character, which breaks REST GET RaaS resolution.
3.  Choose a Data Source appropriate for your target audience:
    -   For manager views (headcount, open roles, team time off), choose a manager-accessible data source such as `Workers for HCM Reporting` with an appropriate filter, or `My Team's Workers`.
    -   For employee self-service views, choose a self-service data source or prompt/filter keyed to the current user.
4.  On the **Advanced** tab, under **Web Service Options**, select **Enable As Web Service**.
5.  On the **Share** tab, share the report definition specifically with the security groups (`Manager`, `HR Partner`, or `All Employees`) who will call it—never leave it restricted solely to the report author.
6.  Click **OK**.

### 2\. Inspect Prompt XML Aliases and Copy the JSON URL

1.  From the custom report’s related actions menu, select **Web Service > View URLs**.
2.  Populate sample values for any required prompts and click **OK**.
3.  Right-click the **JSON** link and copy the URL.
4.  Check the **Prompts** tab of the report definition for exact **Label for Prompt XML Alias** names:
    -   Single-instance Workday ID prompts pass `%21WID=<32-char-WID>` (URL-encoded `!WID=`).
    -   Multi-instance prompts separate WIDs with `!`: `Location%21WID=<WID_1>!<WID_2>`.
    -   Boolean prompts pass `1` or `0` (for example, `Include_Subordinate_Organizations=1`).

### 3\. Register or Scope the User-Delegated API Client

Follow [How to Configure User-Delegated OAuth 2.0 Authorization Code Grant in Workday](https://kiweely.com/guides/workday-authorization-code-grant-user-delegated-oauth-setup) to register an API client via **Register API Client**. On **Scope (Functional Areas)**, include **Include Workday Owned Scope** plus every Functional Area covering the report’s data source and calculated/related fields (for example, `Staffing` and `Time Off and Leave`).

### 4\. Call the RaaS Endpoint with the Worker’s Bearer Credential

Pass the employee’s or manager’s OAuth 2.0 Bearer credential in the HTTP `Authorization` header—no Basic auth username or password is sent:

Works

```
GET /ccx/service/customreport2/gms/lmcneil/Organization_Headcount?Organization%21WID=cb550da820584750aae8f807882fa79a&Include_Subordinate_Organizations=1&format=json HTTP/1.1
Host: services1.wd3.workday-host.example
Authorization: Bearer 7c3obrknwd6nnkxv0r64jdpbx
Accept: application/json
```

Workday returns structured `Report_Entry` JSON containing **only** the workers and columns permitted for that authenticated manager:

Works

```
{
  "Report_Entry": [
    {
      "Employee_ID": "21004",
      "Worker": "Jordan Alvarez",
      "Business_Title": "Warehouse Lead",
      "Supervisory_Organization": "Warehouse 4"
    }
  ]
}
```

## Troubleshooting Empty `Report_Entry` Arrays and `401`/`403` Responses

-   **`401 Unauthorized`:** Check that you are hitting the `services1` web-services hostname shown in **View URLs** (not the UI browser hostname) and that the Bearer access credential has not expired ([refresh lifecycle guide](https://kiweely.com/guides/workday-oauth-refresh-token-expiration-rotation-revocation)).
-   **`403 Forbidden` / Not Authorized:** Verify three items: (a) the custom report’s **Share** tab includes the caller’s security group, (b) the caller’s security group holds **Report/Task `View`** permission on the Data Source domain, and (c) the API client’s **Scope (Functional Areas)** covers the Data Source’s Functional Area.
-   **`200 OK` with `"Report_Entry": []`:** The call succeeded, and Workday’s row-level security filtered out every row for that persona (for example, a standard employee calling a report built on a manager-only constrained domain, or a prompt WID pointing to an organization outside the manager’s supervisory hierarchy).
-   **Ownership Continuity:** If the employee who originally authored the RaaS report leaves the company, run **Transfer Ownership of Custom Reports** (note that changing the owner updates the `<report_owner>` segment in REST RaaS URLs, whereas the SOAP `urn:com.workday.report/Report_Name` namespace stays constant).

Both [Kiweely Bridge](https://kiweely.com/bridge) (coming next, exposing existing custom RaaS reports alongside live WQL and REST inside Claude, ChatGPT, and Gemini) and [Kiweely Leaf](https://kiweely.com/leaf) (coming next, powering custom manager and employee screens) invoke RaaS strictly with each signed-in worker’s own user-delegated OAuth credential rather than a shared ISU.

## Frequently asked questions

### Does the username in a Workday RaaS URL determine whose security runs?

No. The <owner\_username> segment in /ccx/service/customreport2/<tenant>/<owner\_username>/<report\_name> identifies only the report owner's namespace. Workday always evaluates data source, row, and field security against the authenticated caller presenting the OAuth Bearer credential.

### What happens if a report column is secured to a domain the signed-in employee cannot view?

Workday executes the report for the rows the employee is authorized to see and omits or blanks out any restricted columns—the exact same behavior as running the custom report inside the Workday UI.

### Why does a GET RaaS request fail when the report owner's username contains a backslash?

Workday requires that the report owner's username contain no backslash (\\) characters for REST-based GET RaaS URLs to resolve properly. Transfer report ownership to a clean Workday account if needed.

### Do I have to share the custom report with worker security groups as well as enabling Web Services?

Yes. On the Share tab of the custom report definition, share the report with the Authorized Users or security groups (such as Manager or All Employees) who will invoke it, in addition to checking Enable As Web Service on the Advanced tab.

## Sources checked

-   [Workday Admin Guide — Concept: Reports as a Service (RaaS)](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/reports-as-a-service-raas-/dan1370796320263.html)
-   [Workday Admin Guide — Concept: Accessing RaaS Output](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/reports-as-a-service-raas-/dan1370797813643.html)
-   [Workday Admin Guide — Register API Clients](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/oauth/dan1370797831010.html)

## Related guides

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

-   [### Register API Client vs. Register API Client for Integrations in Workday Use Register API Client with Authorization Code Grant and PKCE when external apps act on behalf of a signed-in worker. Reserve Register API Client for Integrations for headless background jobs bound to a single Integration System User.](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)
-   [### Scoping Workday API Client Functional Areas for Least-Privilege Access Workday API Client Scope (Functional Areas) acts as a hard ceiling, never a permission grant: an API request succeeds only when the Functional Area is enabled on the client AND the signed-in worker’s security groups hold permission on the underlying domain or business process.](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping)
-   [### Auditing External API Calls in Workday Sign-On History and Activity Logs Trace external Workday OAuth sign-ins and API requests using four native tools: Signons and Attempted Signons for auth events, View User Activity for 30-day read/write/download calls, View API Clients for client inventory, and View User or Task or Object Audit Trail for mutations.](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)
-   [### How to Configure User-Delegated OAuth 2.0 Authorization Code Grant in Workday Register a user-delegated Workday OAuth 2.0 client using Register API Client with Authorization Code Grant, PKCE (S256), and Bearer credentials so external applications authenticate employees through SSO and run under their own Workday permissions.](https://kiweely.com/guides/workday-authorization-code-grant-user-delegated-oauth-setup)

### More guides on Integrations and APIs

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

-   [Updating Preferred Name, Pronouns, and Contact Information via the Workday Person API](https://kiweely.com/guides/workday-person-api-legal-preferred-name-contact-updates)
-   [Restricting Workday OAuth Token Use by IP with Maintain IP Ranges](https://kiweely.com/guides/workday-maintain-ip-ranges-manage-authentication-policies-api)
-   [Why Browser Single-Page Apps Hit CORS and Token Limits Against Workday APIs—and How to Fix It](https://kiweely.com/guides/workday-cors-browser-api-calls-why-backend-pass-through-needed)
-   [Parsing Workday Business Process Custom Validation Errors Returned by REST and SOAP APIs](https://kiweely.com/guides/workday-business-process-validation-errors-rest-soap-responses)
-   [How Workday Audits Business Processes Initiated via REST or SOAP Web Services](https://kiweely.com/guides/workday-business-process-audit-trail-initiated-via-web-service)
-   [Approving, Denying, and Sending Back Workday Business Process Steps via REST and SOAP APIs](https://kiweely.com/guides/workday-business-process-approve-deny-rest-soap-api)
-   [How Workday Studio PutIntegrationMessage Severity Levels Control Completed-with-Warnings vs. Aborted Runs](https://kiweely.com/guides/workday-studio-error-severity-critical-warning-abort)
-   [How to Fix Workday Studio SDKProfile Not Current and Unsigned Software Startup Errors on Mac and Windows](https://kiweely.com/guides/workday-studio-sdkprofile-not-current-unsigned-macos-errors)

### From the blog on Integrations and APIs

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

-   [Turning a Messy Client Spreadsheet into a Clean Workday EIB Load in One Conversation](https://kiweely.com/blog/messy-spreadsheet-to-workday-eib-load-with-ai)
-   [Workday REST API vs. SOAP Web Services: Why Setup Work Still Needs the Task Screen](https://kiweely.com/blog/workday-rest-api-vs-soap-coverage-gaps)
-   [Untangling Inherited Workday Studio Integrations: A Practical Modernization Playbook](https://kiweely.com/blog/untangling-inherited-workday-studio-integrations)

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