---
title: "How do I secure Workday RaaS access for an internal LLM or…"
description: "Split ISUs by data area, disable UI sessions, prefer user OAuth, and keep RaaS behind Workday domain security."
url: https://kiweely.com/guides/workday-raas-for-ai-agents-security
---

# How do I secure Workday RaaS access for an internal LLM or AI agent?

Split Integration System Users by data area, select Do Not Allow UI Sessions, grant only the report domains each agent needs, and prefer the initiating user’s access token when a person is in the loop. RaaS still obeys domain security.

-   **Checked** against Workday on November 17
-   Applies to **Workday RaaS, Integration System Users**
-   4 min read
-   Published November 17
-   By Kiweely

An internal LLM that reads Workday through Reports-as-a-Service still runs as a Workday principal. Security is the ISU, the Integration System Security Group, the domains on that group, and whether a human user’s token is in the call path. Workday’s Integration App Security page says RaaS inherits the same configurable security model as REST, SOAP, and WQL.

## Design the access model first

| Pattern | When to use | Workday basis |
| --- | --- | --- |
| Initiating user OAuth / access token | A person starts the agent turn and should only see what they may see | Default Access Token From Initiating User for integration apps; Workday prefers this over ISU auth for Integration apps |
| Dedicated ISU for a RaaS report set | Unattended jobs, batch enrichment, or a fixed report catalog | Create Integration System Users for Apps; one ISSG with only the required domains |
| Multiple ISUs split by data area | Privileged payroll or compensation reports must not share a directory-reporting account | Live Data Query guidance: unique ISU per unique security combination |
| ISU on a page that shows calculated results | Rare; user must not see the underlying restricted rows | Concept: ISU Authentication example use case |

Prefer the initiating user’s token whenever a human is present. Workday says ISU authentication is a security exception because ISU access often does not match end-user tenant configuration. If you must use an ISU for an Integration app, do it only when you need a different ISU than the one that launches the integration.

## RaaS setup that an agent can call safely

1.  Copy each standard report you need into a custom report, then enable that custom report as a web service. Workday warns that updates to a standard report can break consumers.
2.  Confirm the report owner’s username has no backslash character; otherwise GET RaaS requests fail.
3.  Use the stable namespace form Workday publishes for apps: `https://api.workday.com/raas/{user}/{report_name}`.
4.  Choose an output format the agent can parse. JSON and CSV are the usual system-to-system choices. RSS is for feed readers with HTTP basic authentication.
5.  Build or reuse an ISU whose ISSG has only the domains those reports require. Grant View for GET-style read access. Activate Pending Security Policy Changes.
6.  On Create Integration System User, keep Session Timeout Minutes at zero and select Do Not Allow UI Sessions. Learning and Live Data Query setup docs both treat that checkbox as required for integration accounts.
7.  Do not hand the agent a human administrator password. RSS Basic Auth still uses a Workday username and password; put that on an ISU that cannot open the UI.

## Split ISUs by area

Workday’s Live Data Query ISU page states the rule in plain language: if every downstream system needs the same data, one ISU can be enough; if some need public reporting and others need privileged information, use two or more ISUs. Cloud Connect for Learning states the same policy for integrations: ISUs must be unique across integrations, and each ISU should have only the appropriate access.

Apply that to an AI agent estate the same way:

-   Directory or org-chart RaaS on a narrow read ISU.
-   Compensation or payroll RaaS on a separate ISU and ISSG.
-   Write or SOAP side effects, if any, on a third account, never on the read RaaS ISU.

## What the agent must not do

-   Call RaaS with a shared “super ISU” that can open every domain in the tenant.
-   Store a UI-capable user’s password for unattended pulls.
-   Treat a successful HTTP 200 as proof the wrong person could not have seen the rows. Domain security on the token still decides the dataset.
-   Use ISU authentication on a page without also checking the signed-in user’s roles when the page exposes restricted calculations. Workday calls out that extra check and the performance cost.

## Failure modes

| Symptom | Cause | Fix |
| --- | --- | --- |
| 403 from RaaS | Missing Report/Task View on the domain | Grant the ISSG View and activate |
| Agent sees another org’s workers | Unconstrained ISSG with broad worker domains, or wrong data source filter | Narrow domains; use role-filtered report design Workday documents for supervisors |
| Session dies mid-batch | Session Timeout Minutes not zero | Set timeout to zero on the ISU |
| Someone signed in as the ISU in a browser | Do Not Allow UI Sessions unchecked | Select the checkbox |

## Frequently asked questions

### Is Basic Auth on RaaS enough for an LLM?

It authenticates the call. It does not limit fields by itself. Domain security on the principal decides the rows. Prefer an ISU with Do Not Allow UI Sessions over a person’s account.

### Should the agent always run as an ISU?

No. When a person starts the work, Workday recommends the initiating user’s access token for Integration apps. Reserve ISUs for unattended or deliberately elevated paths.

### Can one RaaS URL serve every agent prompt?

Technically yes. Operationally no. Split reports and ISUs so a prompt about headcount cannot authenticate as the compensation reader.

## Sources checked

-   [Concept: Reports-as-a-Service (RaaS)](https://developer.workday.com/documentation/hto1529968349582/ConceptReportsasaServiceRaaS)
-   [Concept: Integration App Security](https://developer.workday.com/documentation/GUID-3586727d-613d-4d19-a27b-7e51c70c9ca8/ConceptIntegrationAppSecurity)
-   [SOAP API Authentication and Security](https://developer.workday.com/documentation/GUID-4c354bdb-06cd-461d-a632-ea8303beaedb-enHYPHENus/SOAPAPIAuthenticationandSecurity)
-   [Concept: ISU Authentication](https://developer.workday.com/documentation/GUID-cb3e0fcd-bb97-4005-8d10-3a02e88dab71-enHYPHENus/ConceptISUAuthentication)
-   [Create Integration System Users for Apps](https://developer.workday.com/documentation/GUID-f8d46604-e156-492f-a324-62ed2f6496f7/CreateIntegrationSystemUsersforApps)
-   [Set Up Live Data Query ISU Authentication in Workday](https://doc.workday.com/admin-guide/en-us/workday-data-cloud/data-out/workday-live-data-query-/set-up-live-data-query-isu-authentication.html)
-   [Steps: Set Up Integration System User Security for Cloud Connect for Learning](https://doc.workday.com/admin-guide/en-us/human-capital-management/learning/learning-content/cloud-connect-for-learning/fey1646155264903.html)

## Related guides

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

-   [### Should each Workday AI integration use its own ISU with no UI sessions? Workday’s integration setup pattern is one ISU and one Integration System Security Group per integration, with only the domains that integration needs. Select Do Not Allow UI Sessions and keep Session Timeout Minutes at zero so the account cannot sign in through the UI and does not expire mid-run.](https://kiweely.com/guides/workday-isu-per-area-no-ui-sessions-for-agents)
-   [### How do I set an Integration System Security Group for an Integration System User? An Integration System Security Group is the security group built for an ISU. Create constrained or unconstrained ISSG, add the ISU as the only member type allowed, assign domain and business process permissions, and activate pending security policy changes before you run the integration.](https://kiweely.com/guides/workday-issg-for-integration-system-users)
-   [### SOAP vs RaaS Basic Auth vs OAuth: which Workday credentials do I use? API Gateway SOAP and Extend calls use OAuth Bearer. Classic SOAP web services still expect username@tenant when Workday returns Customer id was not specified. RaaS RSS and Basic Auth credentials use a Workday username and password. Match the credential to the endpoint, not to habit.](https://kiweely.com/guides/workday-soap-vs-raas-vs-oauth-authentication)
-   [### Should I use RaaS, WQL or the REST API to extract data from Workday? Use RaaS for a saved report’s output, WQL for a filtered, grouped or paged extract of up to 1 million rows, and REST for small, low-latency reads of one resource. Limits and sources are in the table.](https://kiweely.com/guides/workday-raas-wql-rest)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [Set up Workday Agent System of Record for HRIS admins](https://kiweely.com/guides/workday-asor-setup-for-hris-admins)
-   [Financials and payroll prompts for the Workday Deployment Agent](https://kiweely.com/guides/workday-ai-prompt-library-financials-payroll)
-   [HCM prompt library for Workday implementers using Deployment Agent](https://kiweely.com/guides/workday-ai-prompt-library-hcm-implementers)
-   [Stop or audit a Workday AI agent: an admin runbook](https://kiweely.com/guides/stop-audit-workday-ai-agent-admin-runbook)
-   [Workday Developer Agent Prompt Templates That Hold](https://kiweely.com/guides/workday-developer-agent-prompt-templates)
-   [A Learning Path on a Workday Build Personal Tenant](https://kiweely.com/guides/workday-build-personal-tenant-learning-path)
-   [Build Your First Workday Extend App with Developer Agent](https://kiweely.com/guides/first-workday-extend-app-developer-agent)
-   [What counts as Workday test evidence when an agent helped](https://kiweely.com/guides/workday-uat-evidence-pack-ai-agents)

### From the blog on Custom agents and Workday AI

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

-   [Workday Deployment Agent vs a desktop Workday agent](https://kiweely.com/blog/deployment-agent-vs-desktop-workday-copilot)
-   [Workday AI testing tools versus tenant chat](https://kiweely.com/blog/workday-ai-testing-tools-vs-tenant-copilots)
-   [Workday as the system of record for agents](https://kiweely.com/blog/workday-system-of-record-for-agents)

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