---
title: "Who can launch a Workday integration? Permissions needed"
description: "Launching a Workday integration needs Modify on the Integration Event domain. Limit it to one integration with an integration system security segment."
url: https://kiweely.com/guides/workday-who-can-launch-integration
---

# Who can launch a specific Workday integration, and what permissions does that user need?

To launch an integration, a user needs Modify on the Integration: Integration Event domain. To limit that to one integration, grant it through a segment-based security group whose segment holds only that integration. Integrations: EIBs, Integration Build and Integration Debug aren’t needed.

-   **Checked** against Workday on November 16
-   Applies to **Workday integrations and EIBs**
-   5 min read
-   Published November 16
-   By Kiweely

## Which permission lets someone launch an integration?

Modify on the **Integration: Integration Event** domain. Workday’s description of the domain is “This domain provides access to launching integrations and viewing their status in the process monitor.” The Security for Administrators course says it in so many words: “To launch an integration, business users must have Modify access to the Integration: Integration Event domain.”

The task people use, **Launch / Schedule Integration**, is secured by three domains: Integration Build, Integration Event and Integration Debug. You don’t need all three: in our test, Modify on Integration Event alone gave the user the task. Workday’s own advice is to use Integration Event, because “Integration Build and Integration Debug would offer much more access than needed for simply launching an integration.” Build covers setting up integration systems, integration IDs and transport protocols; Debug is for debugging Studio integrations.

The admin guide’s integration business process guidelines list a broader set for the initiation step: Modify / Put on Integration Build, Integration Configure, Integration Debug and Integration Event, for “ISU or Integration administrator who launches the integration.” That describes an integration administrator. A business user who only launches needs Integration Event alone, as the test below shows.

The Integration Process Event business process has no initiation entry to secure, so launching is decided by these domains, not by a business process policy. View access on that business process policy is what lets someone see an integration event’s details afterwards.

## How do I let a user launch one integration and no others?

A plain user-based group on Integration Event lets its members launch every integration they can see. To narrow it to one, use segmented security:

1.  **Create Integration System Security Segment.** Add only the integration you want this user to launch. A segment can also be built from an integration category or template, or all systems, if you want a wider set.
2.  **Create Security Group** of type **Segment-Based Security Group**. Under Security Groups, add the group that holds the users (Workday’s course recommends unconstrained groups here, such as a user-based group). Under Access to Segments, add the segment from step 1.
3.  On the Integration: Integration Event domain, run **Edit Domain Security Policy Permissions** and add the new group to **View and Modify**.
4.  Run **Activate Pending Security Policy Changes**. Until you do, Workday says “Your changes have been saved but are not yet in effect.”

Creating and editing segments needs Modify on the Integration Security domain, so this is usually done by a security administrator. Keep in mind Workday’s caution that “a user’s access is the union of all their security group assignments.” If the user is also in a group with unconstrained Integration Event Modify, the segment limits nothing.

## Does the user need anything else?

Not to launch from the Launch / Schedule Integration task. Three things change what the user can do around it:

-   **To open the integration system itself** and launch from its related actions (**Integration > Launch / Schedule**), the user also needs View on **Integration Build**. Without it, opening the integration system returns “The task submitted is not authorized.” Granting Build View through the same segment-based group keeps it to that one system.
-   **The data the integration reads or writes.** When an integration has no integration system user, it runs as the person who launched it. For an outbound EIB, that person needs access to the source report. For an inbound EIB, Workday “assesses the security of the business user running the integration”, so they need Put on the domain behind the web service operation, or the Initiating Action (Web Service) step of the business process it starts.
-   **Integrations: EIBs is not needed.** Workday describes it as access “to view EIB integration templates. A security group must have additional security permissions to modify or launch integrations.” It’s for people who configure EIBs.

## What happens when we test it in a tenant?

We ran this in a Workday test tenant with a user who had no integration access at all: a call center operator role with nothing else. We made four EIBs and gave the user launch rights to one of them only, through the steps above. Every result below was taken while signed in as that user with Start Proxy.

**Before any grant**, searching for the task returned `No results for "Launch / Schedule Integration"`.

**With only Integration Event View and Modify, through a segment holding one EIB**, the Launch / Schedule Integration prompt listed that one EIB and none of the other three. The launch finished with “Interface completed successfully!” and an output file. The event showed Initiated By as the user and Ran As as the same user, because the EIB had no integration system user.

**Opening one of the other EIBs directly**, from a link, failed with:

`Error running task: instance (625$211) does not meet the restrictions defined for this task (2998$599).`

The instance ID is the integration system’s; yours will differ. This is the message that means the user’s segments don’t include that integration.

**Without Integration Build View**, opening the permitted EIB’s own page failed with `The task submitted is not authorized.` Adding Build View through the same segment made the page open, with Integration > Launch / Schedule in its related actions.

**Data access mattered before launch.** One EIB used a report the user couldn’t run. It never appeared in the user’s launch prompt, even when the user had Integration Event Modify for all integrations. An EIB built on a report the user could run appeared at once.

**Removing Integrations: EIBs** changed nothing. The user still launched the permitted EIB.

## How do I see who can launch a specific integration today?

-   Run **View Security for Securable Item** on the Launch / Schedule Integration task. It lists the three securing domains; follow each domain to its policy to see which groups have Modify.
-   On the Integration Event policy, open each segment-based group to see its segments, and each segment to see which integration systems it holds.
-   For one person, **View Security Groups for User** shows every group they’re in. Remember the union rule: one broad group anywhere gives them every integration.

## What about scheduled integrations?

Workday’s Securing Connectors course: “When you run the Launch / Schedule Integration task, the user who configures the schedule automatically owns it.” Transfer ownership of the schedule to the integration system’s integration system user, so the schedule doesn’t depend on a person who may leave. “The ISU must have modify access to the Launch / Schedule Integration task to own an integration schedule,” which again means Integration Event.

## Where to go from here

If the integration runs as an integration system user and fails with an authentication error, [Workday ISU authentication errors](https://kiweely.com/guides/workday-isu-authentication-errors) goes through each cause. Setting up that user and its API client is in [Workday integration system user and API client](https://kiweely.com/guides/workday-integration-system-user-api-client). If you’re choosing how the integration should start in the first place, see [integration system vs business process templates](https://kiweely.com/guides/workday-integration-system-vs-business-process-templates). For an Extend app that calls Workday as an ISU, see [simplified ISU errors](https://kiweely.com/guides/workday-simplified-isu-errors). And when an inbound EIB launches but rows fail, [Workday EIB load errors](https://kiweely.com/guides/workday-eib-load-errors) covers the messages.

## Frequently asked questions

### Which domain lets a user launch a Workday integration?

Integration: Integration Event, with Modify. Workday's description of the domain is that it provides access to launching integrations and viewing their status in the process monitor.

### Can I let a user launch one integration and no others?

Yes. Put that integration alone in an integration system security segment, make a segment-based security group from the segment and the users' group, give it View and Modify on Integration Event, and activate the pending security policy changes.

### Does the user need the Integrations: EIBs domain to launch an EIB?

No. Workday describes that domain as access to view EIB integration templates. In our test a user launched an EIB without it.

### Whose security does an EIB use when a business user launches it?

The business user's, when the integration system has no integration system user. Our test run showed Ran As set to the user who launched it.

## Sources checked

-   [Security for Administrators: Integrations](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/integrations.html)
-   [Security for Administrators: User Access to Integrations](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/user-access-to-integrations.html)
-   [Creating and Securing Integrations: Securing Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/securing-connectors.html)
-   [Integration Business Process Guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/integration-business-process-guidelines.html)

## Related guides

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

-   [### Integration System template vs Business Process template in Workday Orchestrate Use the Workday Integration System template when an integration system launches the work on a schedule or on demand and you need an integration event with messages and files. Use the Workday Business Process template when a step in one business process event should launch it with that event’s data.](https://kiweely.com/guides/workday-integration-system-vs-business-process-templates)
-   [### Simplified ISU errors in Workday Extend: 500s and “ISU is not configured in this tenant for appRefId” The simplified ISU scheme is configured per tenant. An endpoint fails when, in that tenant, no ISU with the SMD’s username is assigned to the app in App Manager, its API client wasn’t created, a non-Development tenant isn’t authorized on the client, or the ISU’s security group lacks the domain.](https://kiweely.com/guides/workday-simplified-isu-errors)
-   [### Workday ISU or API client 401, invalid\_client, invalid\_grant These errors usually blame the token, but the real cause is the ISU’s own account, its security group’s activation, or the wrong client task — not a corrupted credential.](https://kiweely.com/guides/workday-isu-authentication-errors)
-   [### Why did my Workday EIB load fail? Fix Invalid ID Value and field restriction errors Open the integration event on View Background Process. For Completed With Errors, select Number of Errors to read each row’s message. Invalid ID Value is a wrong Reference ID; ‘does not meet the restrictions’ names the field, and in Workday’s example the launching user lacked security for it.](https://kiweely.com/guides/workday-eib-load-errors)
-   [### How do I set up an integration system user and API client in Workday so an external app can authenticate? Create the ISU, put it in an Integration System Security Group, grant domain permissions and activate them, register the client for integrations, then generate its refresh token and pick the ISU as the Workday account.](https://kiweely.com/guides/workday-integration-system-user-api-client)

### More guides on Integrations and APIs

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

-   [Write Your First Workday Studio AUnit Tests Before Changing the Assembly](https://kiweely.com/guides/write-first-workday-studio-aunit-tests)
-   [How a Workday Sandbox Refresh Affects Registered API Clients and Redirect URLs](https://kiweely.com/guides/workday-api-client-disabled-tenants-sandbox-refresh-impacts)
-   [Register API Client vs. Register API Client for Integrations in Workday](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)
-   [Workday API Attachment Rules: File Size Limits, Allowed MIME Types, and Doctor’s Note Uploads](https://kiweely.com/guides/workday-attachment-upload-virus-scan-size-mime-rules-api)
-   [Scoping Workday API Client Functional Areas for Least-Privilege Access](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping)
-   [Submitting and Validating Time-Off Requests with the Workday Absence REST API](https://kiweely.com/guides/workday-absence-management-rest-api-request-time-off)
-   [Reading Current Benefits Elections and Dependents Through Workday Self-Service APIs](https://kiweely.com/guides/workday-view-benefits-elections-dependents-beneficiaries-api)
-   [Auditing External API Calls in Workday Sign-On History and Activity Logs](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)

### From the blog on Integrations and APIs

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

-   [Nothing Kept After a Run: Zero-Retention Workday Integrations](https://kiweely.com/blog/nothing-kept-after-a-run-zero-retention-integrations)
-   [Retire Workday Studio and EIB Debt with External Integrations](https://kiweely.com/blog/retire-workday-studio-eib-debt-with-external-integrations)
-   [When the Answer Is Chat, a Screen, or a Running Integration](https://kiweely.com/blog/when-the-workday-job-is-chat-a-screen-or-an-integration)

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