Integration access scoping is opt-in. Every workflow starts in its workspace’s Default package and every integration starts open, so nothing changes until someone with the Manage integration access permission restricts an integration.
How it works
A package groups workflows with the integrations they’re allowed to use. Restricting an integration to one or more packages changes which workflows can use it and who can publish the workflows that depend on it:- Workflows in a linked package keep access. When a workflow picks an integration automatically, it prefers one that’s linked to its package.
- A workflow that isn’t in a linked package can’t use the integration. What happens depends on how the workflow reaches for it:
- If it explicitly targets the integration, the run fails to start, and the error names the integration and the package.
- If it would only pick the integration up automatically, the run leaves the integration out instead of failing.
- If the integration is passed in by an ID, it’s refused when the workflow tries to use it.
- Publishing and test-running drafts are gated; editing isn’t. For a package that links a restricted integration, only people on its access list can publish or test-run its drafts. Ordinary edits still follow your workspace’s normal workflow permissions.
- Linking a restricted integration to another package is limited. People with Manage integration access can link it to any package. Anyone else who can add the integration can link it only to packages they can publish into. Being listed under Who can add this integration to packages doesn’t let anyone see the integration. They still need a role that can view integrations.
Who can manage integration access
Restricting an integration, creating and managing packages and who has access to them, and choosing who can add a restricted integration to packages all require the Manage integration access permission. Organization admins have it in every workspace. People who can publish into a package can also change which integrations it links. Without the permission, the integration’s Integration access section is read-only.Set it up
1
Create a package
Go to Settings → Integrations → Packages and select Create package, then give it a name. New workflows start in the Default package, which can’t be renamed or deleted.
2
Give the package access
On the package, select Edit access and add the people or groups who should be able to publish and test-run its workflows. A package with no one on its Has access list can’t keep a restricted integration, so set this before you restrict.
3
Link the integration to the package
Open the integration, go to its Settings tab, and in Integration access set Workflow access to Only workflows in these packages. Under Packages that link this integration, select Add to package… to link the integration to the package or packages that should keep access. Review and restrict… stays unavailable until you link at least one package.
4
Review and restrict
Select Review and restrict…. The preview lists the Packages that keep access and the Workflows that lose access, with the reason each workflow is affected. To keep a listed workflow working, select it. If only one linked package can take it, the dialog names that package. Otherwise, choose one under Move selected workflows into. Then confirm with Restrict integration. If you selected workflows to move, the button reads Move with the number of workflows, followed by and restrict.
The preview can’t detect workflows that choose an integration at run time from their inputs. Check those workflows yourself before you restrict.

