Skip to content
KiweelyKiweelyKiweely

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
  • Applies to Workday Studio and integration security
  • 3 min read
  • Published
  • By Kiweely
On this page

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
ErrorPermission to launch denied Domain permission Workday citesPut on Integration Event, Integration Build, or Integration Debug
ErrorPermission to deploy denied Domain permission Workday citesModify on Integration Build
ErrorPermission to deploy denied (integration contains a delivery or retrieval service) Domain permission Workday citesAdditional Put on Business Process Administration, Manage: Business Process Definitions, or iLoad Web Services
ErrorAccess to My Reports denied Domain permission Workday citesConfigurable 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
TaskDeploy a Studio integration Domain accessIntegration Build
TaskConfigure integration services Domain accessIntegration Configure
TaskDebug a Studio integration Domain accessIntegration Debug
TaskLaunch or schedule an integration Domain accessIntegration Event
TaskView resulting integration events and output documents Domain accessIntegration Event
TaskView integration reports Domain accessIntegration Reports
TaskView/edit subscriptions Domain accessIntegration 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).

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). Start free.

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.