---
title: "Permission to launch a Workday integration: which domains…"
description: "Studio’s “Permission to launch denied” means Put on Integration Event, Build, or Debug. Deploy needs Modify on Integration Build."
url: https://kiweely.com/guides/permission-to-launch-workday-integration
---

# Permission to launch a Workday integration: which domains Studio checks

To launch an integration from Workday Studio you need Put permission on Integration Event, Integration Build, or Integration Debug. Deploy is a different domain check.

-   **Checked** against Workday on November 19
-   Applies to **Workday Studio and integration security**
-   3 min read
-   Published November 18
-   By Kiweely

When Workday Studio returns **Permission to launch denied**, Workday’s connection-error reference says the signed-in user must be in a security group with **Put** permission on one of these domains: **Integration Event**, **Integration Build**, or **Integration Debug**. That is separate from deploy permission and from delivery/retrieval-service extras.

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect: it sets up integration security in the tenant and tests it as the user who launches. See how it works below.

## Studio connection errors that are really security

From **Reference: Connection Errors**:

| Error | Domain permission Workday cites |
| --- | --- |
| Permission to launch denied | Put on Integration Event, Integration Build, or Integration Debug |
| Permission to deploy denied | Modify on **Integration Build** |
| Permission to deploy denied (integration contains a delivery or retrieval service) | Additional Put on Business Process Administration, Manage: Business Process Definitions, or iLoad Web Services |
| Access to My Reports denied | Configurable security on My Reports integration documents for that account |

Contact your Workday system administrator for the group membership—Studio itself cannot grant these domains.

## How launch differs from other integration tasks

Workday Education’s Studio assembly topic maps domains to jobs:

| Task | Domain access |
| --- | --- |
| Deploy a Studio integration | Integration Build |
| Configure integration services | Integration Configure |
| Debug a Studio integration | Integration Debug |
| Launch or schedule an integration | Integration Event |
| View resulting integration events and output documents | Integration Event |
| View integration reports | Integration Reports |
| View/edit subscriptions | Integration Subscriptions |

So a developer who can **deploy** (Modify on Integration Build) may still fail to **launch** until Put exists on Integration Event (or Build/Debug per the connection-error list). An Integration System User used for runtime similarly needs Put on Integration Event in the Integration functional area for launch-style event work—see your ISU setup for the specific integration.

## Practical fix sequence

1.  Confirm the Studio connection uses the intended Workday account (tenant names are case-sensitive on auth failures).
2.  Ask security to place that account in a group with **Put** on **Integration Event** (minimum for launch/schedule in the assembly table; connection errors also accept Build or Debug).
3.  If deploy also fails, add **Modify** on **Integration Build**.
4.  If the assembly includes delivery or retrieval services, add the extra Put domains listed above.
5.  Run **Activate Pending Security Policy Changes** after policy edits.
6.  Retry launch from Cloud Explorer on the workday-in transport.

This page answers “who can launch.” Restricting launch to **one** named integration system (not all integrations on the domain) requires segmented security on integration systems—a separate design in Workday’s security-for-integrations material—not just unconstrained Put on Integration Event.

## Where Kiweely fits

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect. It sets up security groups and business process security policies in your tenant, activates the changes and tests as the real users.

In a recorded run in Kiweely’s own Workday Development tenant (with fictional sample data, not a customer result), Vine built a training-approval Extend app from a plain request, set up its access (Employee As Self, Manager) and the approval’s business process security policy, activated the security changes, added the Manager step to routing, and tested it as the employees and managers through Start Proxy. It took 1 hour 51 minutes from sign-up to the checked result, and the film reports five checks passed ([watch the film](https://youtu.be/hoJV5tq90Ug)).

Vine Free is $0 on a personal developer tenant with $5 of Kiweely Credits included, and Vine Personal ($99/month) and Vine Team ($149/seat/month) connect to any Workday tenant ([pricing](https://kiweely.com/pricing)). [Start free](https://kiweely.com/download).

## Sources checked

-   [Reference: Connection Errors](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-deployment/qju1530541056614.html)
-   [Building an Assembly](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-studio/building-an-assembly.html)

## Related guides

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

-   [### Workday EIB vs Core Connector vs Cloud Connect vs Studio: which to use Use an end-to-end Cloud Connect connector if one exists for the vendor, a Core Connector for a delivered template with change detection, EIB for simple guided loads, and Studio for multiple web service calls or complex error handling.](https://kiweely.com/guides/workday-studio-vs-eib-vs-cloud-connect)
-   [### 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)

-   [What Workday Customer Central is (and isn’t) for implementers](https://kiweely.com/guides/workday-customer-central-for-implementers)
-   [Object Transporter migration workflow: pre-check, first 50, merge vs override](https://kiweely.com/guides/workday-object-transporter-migration-workflow)
-   [What does Workday Studio “Content is not allowed in prolog” mean?](https://kiweely.com/guides/workday-studio-content-is-not-allowed-in-prolog)
-   [Why does Workday RaaS time out for non-admin users but work for admins?](https://kiweely.com/guides/workday-raas-timeout-non-admin-user)
-   [Why does a custom object update return 403 with escaped HTML in the body?](https://kiweely.com/guides/workday-custom-object-patch-403-escaped-html)
-   [Why does Create WCP API Client return 409 for an ISU?](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)
-   [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)

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