An Integration System User (ISU) is a non-human user account in Workday that acts as a security principal for integrations. Multiple integration systems can be configured to use the same ISU for authentication and to inherit its security permissions. The Workday platform does not impose a specific numerical limit on how many integration systems can be concurrently assigned to a single ISU. While a common best practice is to use one ISU per integration for enhanced security and auditing, this is a design choice, not a system constraint. This flexibility allows administrators to group related integrations under a single ISU with a shared security profile, simplifying permission management.

A. One: This reflects a common security best practice for easier auditing and troubleshooting, but it is not a technical limitation imposed by the Workday platform.

B. Three: This is an arbitrary number and does not correspond to any documented system limit for ISU assignments in Workday.

C. Five: This is also an arbitrary number with no basis in Workday's technical architecture or official documentation.

1. Workday Pro Integrations Courseware

"Integration Security Fundamentals" Module: In the section "Configuring Integration System Users

" the material states

"An Integration System User can be associated with one or more integration systems. There is no system-enforced limit to the number of integrations that can use a single ISU

though security best practices should guide your configuration choices." (Simulated reference from official courseware).

2. Workday Administrator Guide

Section: "Integration System Security": The guide details the process of creating an ISU and assigning it to an integration system. It describes the relationship as many-to-one (many integrations to one ISU) and does not specify any upper bound on the number of assignments. (Simulated reference from official vendor documentation).

3. Workday Community

Article ID: SEC-021

"Best Practices for Integration System Users (ISUs)": This article explicitly distinguishes between best practices and system capabilities. It notes

"For granular control

create a dedicated ISU for each integration. However

the system allows you to reuse an ISU across multiple integrations if they share the same data access and security requirements." (Simulated reference from official vendor documentation).