Skip to content
KiweelyKiweelyKiweely

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
  • Applies to Workday RaaS, Integration System Users
  • 4 min read
  • Published
  • By Kiweely
On this page

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
PatternInitiating user OAuth / access token When to useA person starts the agent turn and should only see what they may see Workday basisDefault Access Token From Initiating User for integration apps; Workday prefers this over ISU auth for Integration apps
PatternDedicated ISU for a RaaS report set When to useUnattended jobs, batch enrichment, or a fixed report catalog Workday basisCreate Integration System Users for Apps; one ISSG with only the required domains
PatternMultiple ISUs split by data area When to usePrivileged payroll or compensation reports must not share a directory-reporting account Workday basisLive Data Query guidance: unique ISU per unique security combination
PatternISU on a page that shows calculated results When to useRare; user must not see the underlying restricted rows Workday basisConcept: 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
Symptom403 from RaaS CauseMissing Report/Task View on the domain FixGrant the ISSG View and activate
SymptomAgent sees another org’s workers CauseUnconstrained ISSG with broad worker domains, or wrong data source filter FixNarrow domains; use role-filtered report design Workday documents for supervisors
SymptomSession dies mid-batch CauseSession Timeout Minutes not zero FixSet timeout to zero on the ISU
SymptomSomeone signed in as the ISU in a browser CauseDo Not Allow UI Sessions unchecked FixSelect 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

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.