Skip to content
KiweelyKiweelyKiweely

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

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
ControlOne ISU per area SettingSeparate accounts WhyLimits blast radius when a prompt or job is compromised
ControlOne ISSG per ISU pattern SettingGroup named for that integration WhyEducation: one integration, one ISSG
ControlSession Timeout Minutes Setting0 WhyPrevents mid-run expiry
ControlDo Not Allow UI Sessions SettingSelected WhyBlocks browser sign-in as the system account
ControlDomain grants SettingMinimum for that area WhyWorkday Delivery Assurance expects least privilege
ControlHuman admin accounts SettingNot used for unattended pulls WhyPeople 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

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.