---
title: "Should each Workday AI integration use its own ISU with no…"
description: "Create one Integration System User per integration area, keep Session Timeout at zero, and select Do Not Allow UI Sessions."
url: https://kiweely.com/guides/workday-isu-per-area-no-ui-sessions-for-agents
---

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

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

Yes. Workday’s integration security material tells you to create one Integration System User per integration system, pair it with one Integration System Security Group, and give that group only the access the integration needs. For AI agents and other unattended callers, treat each data area or integration as its own system: its own ISU, its own ISSG, and no UI sign-in.

## Why not one shared ISU

Workday Education’s Creating and Securing Integrations chapter states the reasons business users are the wrong owners for integrations: people leave, change jobs, and rarely hold every domain an integration needs. The same chapter says you create only one ISU per integration system, and that ISU only needs access for that integration.

Live Data Query repeats the split for data access combinations. If all consumers need the same tables, one ISU can suffice. If some need public reporting and others need privileged fields, use two or more ISUs. Cloud Connect for Learning adds that ISUs must be unique across integrations.

For an agent estate, “area” means a bounded permission set: for example recruiting read, payroll read, or benefits write. Do not share a recruiting ISU with a payroll RaaS job because the prompts are in the same chat product.

## Create the ISU the way Workday documents it

1.  Run Create Integration System User. You need the Integration Security domain.
2.  Set a unique username. Workday’s examples use names such as `_Learning_ISU` or `isu-lmcneil-ldq`. Education materials suggest matching the integration name with an `_ISU` suffix.
3.  Keep Session Timeout Minutes at zero so the session does not expire before the job finishes. Create Integration System Users for Apps, Learning, Peakon, and Live Data Query all keep that default of zero.
4.  Select Do Not Allow UI Sessions. Peakon, Learning, calendar integrations, and Live Data Query all document this checkbox as the way to prevent the ISU from signing into Workday through the UI.
5.  Do not select Require New Password at Next Sign In for an unattended account (Live Data Query).
6.  Create Integration System Security Group (Unconstrained) unless you have a deliberate constrained design. Add only this ISU. Only ISUs can be members of ISSGs.
7.  Maintain Domain Permissions for Security Group. Grant View/Modify or Get/Put only for the domains this area needs. Activate Pending Security Policy Changes.
8.  Assign the ISU to the integration system, schedule, app, or API client that owns the area.

## Checklist for agent operators

| Control | Setting | Why |
| --- | --- | --- |
| One ISU per area | Separate accounts | Limits blast radius when a prompt or job is compromised |
| One ISSG per ISU pattern | Group named for that integration | Education: one integration, one ISSG |
| Session Timeout Minutes | `0` | Prevents mid-run expiry |
| Do Not Allow UI Sessions | Selected | Blocks browser sign-in as the system account |
| Domain grants | Minimum for that area | Workday Delivery Assurance expects least privilege |
| Human admin accounts | Not used for unattended pulls | People change roles; ISUs do not |

## What this does not replace

Selecting Do Not Allow UI Sessions does not remove domain grants. An ISU with broad Get permission on worker and compensation domains is still overpowered even if it cannot open the UI. Concept: ISU Authentication also warns that ISU access often fails to match end-user security, so pages and apps that elevate through an ISU need their own checks.

## Failure modes

-   Shared ISU across three agents. A revoke or password rotation takes all three offline, and every agent inherits the widest grant.
-   UI sessions allowed. Operators can sign in as the integration account and act outside the intended API path.
-   Non-zero session timeout. Long RaaS or SOAP batches die with expired sessions.
-   ISU created, ISSG never granted domains. Calls authenticate and then fail authorization.

## Frequently asked questions

### Constrained or unconstrained ISSG?

Workday Education says most integrations use unconstrained ISSGs. Use constrained when the integration should see only workers in organizations you assign. Extend app setup docs commonly create Integration System Security Group (Unconstrained).

### Does simplified ISU authentication change this pattern?

No. Simplified ISU changes how an Extend app obtains the token. You still create the ISU, ISSG, and domain grants the same way, and you still select Do Not Allow UI Sessions for unattended accounts.

## Sources checked

-   [Workday Configurable Security](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-configurable-security.html)
-   [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)
-   [Steps: Set Up Workday Integration](https://doc.workday.com/peakon/en-us/workday-peakon-employee-voice/integrations/workday-integration/qdk1635869479224.html)
-   [Concept: ISU Authentication](https://developer.workday.com/documentation/GUID-cb3e0fcd-bb97-4005-8d10-3a02e88dab71-enHYPHENus/ConceptISUAuthentication)

## Related guides

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

-   [### 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)
-   [### How do I migrate a Workday Extend app from WCPISU to simplified ISU? Workday treats WCPISU as legacy. New Extend apps after October 4, 2024 must use simplified ISU. Migrate by assigning the ISU in App Manager, declaring scheme ISU in the SMD, updating PMD authType values, and creating fresh orchestration credentials. You cannot reuse the old WCPISU API client.](https://kiweely.com/guides/workday-migrate-wcpisu-to-simplified-isu)
-   [### 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.](https://kiweely.com/guides/workday-raas-for-ai-agents-security)

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

-   [App Builder vs Claude Code for Workday Developer Agent](https://kiweely.com/blog/app-builder-vs-claude-code-developer-agent)
-   [What to put in a Workday SOW when agents are in scope](https://kiweely.com/blog/workday-implementation-sow-ai-agents)
-   [Can AI agents speed up a Workday implementation? What they do in the tenant today](https://kiweely.com/blog/kiweely-vine-workday-implementation-project)

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