---
title: "How do I set an Integration System Security Group for an…"
description: "Create an ISSG, add only the ISU, grant Get/Put and View/Modify on the domains the integration needs, then activate."
url: https://kiweely.com/guides/workday-issg-for-integration-system-users
---

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

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

An Integration System Security Group (ISSG) is the security group that serves an integration. Workday Education states that one integration has one ISSG, that only Integration System Users can be members, and that you choose constrained or unconstrained when you create the group. The ISSG is what you put on domain security policies and business process security policies so the ISU can Get or Put data.

## Constrained vs unconstrained

| Type | Meaning in Workday Education | Typical use |
| --- | --- | --- |
| Integration System Security Group (Unconstrained) | Access all target instances of a securable item, for example all workers | Most integrations; Extend app setup samples |
| Integration System Security Group (Constrained) | Access a subset, typically workers in organizations the security administrator assigned | Integrations that must stay inside specific orgs |

Create the group with Create Security Group, pick the constrained or unconstrained Integration System type, and name it for the integration. Education suggests matching the integration system name with an `_ISSG` suffix.

## Steps

1.  Create the ISU with Create Integration System User. Keep Session Timeout Minutes at zero. Select Do Not Allow UI Sessions when the account is for integrations.
2.  Create Security Group. Select Integration System Security Group (Unconstrained) or the constrained variant. Add the ISU under Integration System Users.
3.  From the ISSG related actions, open Maintain Domain Permissions for Security Group (or Maintain Permissions for Security Group).
4.  On each required domain, add the ISSG.
    -   Report/Task Permissions: View for read, Modify for write. Integration App Security maps View to GET and Modify to POST, PUT, PATCH, and DELETE for REST.
    -   Integration Permissions: Get replaces View and Put replaces Modify for web service style access. Education notes most outbound integrations only need Get.
5.  If the integration initiates a business process through a web service, add Initiating Action (Web Service) on that business process security policy. If a related business process triggers the integration and it must read event files or values, add View All on that policy.
6.  Run Activate Pending Security Policy Changes.
7.  Assign the ISU to the integration system (Related Actions > Workday Account > Edit on the integration system) and to any schedule that should run as that account.
8.  Test by running the integration as the ISU and comparing results to a known-good run, as Education describes.

## Domain grants to double-check

Education lists common Integration functional area domains. Examples:

| Domain | Why an ISSG might need it |
| --- | --- |
| Integration Event | Launch or schedule; view events and output |
| Integration Build | Create or edit systems; deploy Studio |
| Integration Configure | Configure services |
| Integration Security | Maintain integration system users and segments |
| Integration Reports | View exception and message reports |

Grant only what that integration uses. Selecting Modify includes View. On the integrations section of a policy, put Get-only groups on their own row so you do not accidentally also grant Put.

## Extend apps

Create Integration System Users for Apps follows the same ISSG pattern: Integration System Security Group (Unconstrained), then View/Modify for REST (and Graph data sources) and Get/Put for SOAP in orchestrations. Activate Pending Security Policy Changes before you expect the app’s ISU calls to succeed.

## Failure modes

-   Business user added to an ISSG. Only ISUs can be members.
-   ISSG created, never placed on a domain policy. Authentication works; authorization fails.
-   Put granted for a read-only outbound job. Narrow to Get.
-   Child domain policies inherited more securable items than you reviewed. Drill into securable actions before you approve Modify.
-   Pending security policy changes not activated. The ISSG looks correct and still cannot run.

## Frequently asked questions

### Is an ISSG the same as a user-based security group?

No. An ISSG exists to service an integration and only accepts ISUs. User-based groups hold people such as HR Administrator.

### Do I put the ISSG on every domain the report fields touch?

You put it on the domains that secure the web services, reports, and tasks the integration calls. Inheritance through child policies can expand that set. Review securable items before you grant Modify or Put.

### One ISSG for many ISUs?

Workday’s education pattern is one ISSG per integration system, with the matching ISU. Live Data Query allows adding ISU users to a group, but still designs unique groups when security combinations differ. Prefer one clear group per permission set.

## 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)
-   [Concept: Integration App Security](https://developer.workday.com/documentation/GUID-3586727d-613d-4d19-a27b-7e51c70c9ca8/ConceptIntegrationAppSecurity)
-   [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 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)
-   [### Security Domains for Your First Workday Extend App A security domain file does nothing until you deploy, create the domain security policy, grant a security group, and activate it. Page security should use unconstrained role-based groups. Developer Agent can write the file. It does not configure the tenant.](https://kiweely.com/guides/first-workday-extend-app-security-domains)

### More guides on Integrations and APIs

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

-   [SOAP vs RaaS Basic Auth vs OAuth: which Workday credentials do I use?](https://kiweely.com/guides/workday-soap-vs-raas-vs-oauth-authentication)
-   [Which Object Transporter migration paths does Workday support?](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [Sandbox to Production Object Transporter checklist](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [Object Transporter or Configuration Change Tracker: which moves Workday config?](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)
-   [Why does Object Transporter block single-instance migration from Production?](https://kiweely.com/guides/workday-ox-production-single-instance-limits)
-   [EIB spreadsheet mapping when an AI assistant drafts the load](https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants)
-   [Custom reports and RaaS when an AI assistant is helping you build them](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants)
-   [Run Workday Studio AUnit Before You Accept AI Edits](https://kiweely.com/guides/workday-studio-aunit-before-ai-edits)

### From the blog on Integrations and APIs

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

-   [Kiweely builds, deploys and runs a Workday Studio integration from one request](https://kiweely.com/blog/workday-studio-integration-built-deployed-and-run)
-   [Why does a Workday EIB load fail, and how do you get a clean load the first time?](https://kiweely.com/blog/why-workday-eib-load-fails)
-   [Kiweely builds and runs a Workday Outbound EIB from one request](https://kiweely.com/blog/workday-outbound-eib-integration-built-and-run)

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