Skip to main content

What is an Integrate.io ETL Package Group?

A Package Group lets you group and organize packages together. Think of Package Groups as folders. You can group pipelines by team when many users share the same Integrate.io ETL account, group pipelines by customer, or keep template packages you want to reuse later. Use Package Groups to organize packages based on whatever criteria fit your requirements. To open the feature, click the Package Groups icon in the left navigation.
Package Groups icon in the left navigation menu

Creating a Package Group

To create a Package Group, go to the Package Groups tab and click New Package Group. A modal opens (see image below). Give the Package Group a name and add a description if needed. You can also add packages now if you already have some in mind, or click Create Package Group and add packages later.
New Package Group modal with name and description fields
Package Group creation confirmation with packages listed

Adding Packages to a Package Group

After you create a Package Group, you can add packages to it. Click the triple dot icon on the Package Group, click Edit Package Group, then use the dropdown to add packages. Only packages that do not already belong to a Package Group are available, because a package can belong to one Package Group at a time.
Edit Package Group option in the triple dot menu

Moving a Package to Another Package Group

To move a single package to another Package Group, go to the Packages tab, click the triple dot icon, and click Change Package Group. Packages that don’t belong to any Package Group show Add to Package Group instead.
Change Package Group option on a package in the Packages tab
To move packages in bulk, click Edit Package Group, remove the relevant packages, and save. Then open another Package Group with Edit Package Group and add the packages there.
Removing packages from a Package Group in the edit dialog

Restricting a Package Group to Specific Connection Groups

By default a package group can reference any connection in the account. Account admins can bind a package group to one or more connection groups so packages in the group may only reference connections from those groups. Use this to keep production packages isolated from sandbox connections, separate one team’s connections from another’s, or enforce environment boundaries between package groups. A package group with no binding is unrestricted and continues to see every connection in the account. Adding at least one binding switches the package group to restricted and applies these rules to every package in the group:
  • The connection picker in the package designer lists only connections from the bound connection groups.
  • Saving a package that references a connection outside the bound groups returns a 422 error naming the offending connection. This applies to sources, destinations, execute SQL, and Lookup components (including the bare database_connection_id and cloud_storage_connection_id fields on Lookup).
  • Cloning a package into a restricted package group is blocked when the source references an out-of-bounds connection.
  • Connections that do not belong to any connection group are treated as out of bounds in a restricted package group.
  • Running an existing package that references an out-of-bounds connection fails at run time. Packages last saved before the binding was applied are grandfathered until they are next edited.
Clearing every binding returns the package group to unrestricted.

Configure Connection Access on a Package Group

The Connection access picker is shown on the package group form when you have manageConnectionAccess.
1
Open the package group in Package Groups, or start a new one with New Package Group.
2
Scroll to Connection access. Use the picker to add one or more connection groups. Each added group is listed below the picker with a remove button.
3
Save the package group. The binding replaces the previous set; leaving the list empty saves the package group as unrestricted.

Connection Access Audit Page

Settings > Developer > Connection Access is a read-only, account-wide overview of every package group with its binding state and a count of connections currently out of bounds. Use it to spot restricted package groups whose packages still reference connections outside the binding, then open the offending package group to fix the binding or the package. Only bound (restricted) package groups are scanned. Unrestricted package groups show as No restrictions. Access is gated on manageConnectionAccess. Members without the permission see a “not authorized” message.

Permissions

Editing a package group’s binding is an account-governance action gated on the dedicated manageConnectionAccess permission. Owners and Admins have it by default. On accounts using custom roles, grant manageConnectionAccess to any additional role that should manage bindings. updateWorkspace alone does not grant it: a package-group editor cannot silently change which connections the group’s members can reach.

Managing bindings from the API

The binding is exposed on the account API v2 under a workspace. All calls require an admin API key. Fetch the current binding for a package group:
The response returns connection_group_ids (the bound connection group IDs) and unrestricted (true when the array is empty). Replace the binding set. This call uses full replace-set semantics: rows not present in connection_group_ids are removed, and new IDs are added. Submit an empty array to clear every binding.
Cross-account connection group IDs are rejected with a 422 rather than silently dropped. List the out-of-bounds connection references currently held by packages in a restricted package group:
Each violation names the package, the referenced connection, and the connection group that connection belongs to. Use this report to find packages you need to re-point, or connection groups you need to add to the binding, before a scheduled run hits the run-time check. For an account-wide overview of every package group with its binding state and violation count, call:

Deleting a Package Group

You can delete a Package Group by clicking the triple dot icon on the Package Group and clicking Delete Package Group. Deleting a Package Group will not delete the packages under the Package Group. These packages will no longer belong to a Package Group.
If a custom role is scoped to Specific package groups and you delete the last package group in its scope, the role’s package group scope is automatically demoted to No package groups. Members assigned to that role lose access to every package, job, schedule, and package group until the role is edited to grant a new scope. Review any custom roles that reference a package group before deleting it.

Package Group Summary Bar

Package Group summary bar showing job status counts
Each Package Group shows a summary bar with the following job-related information.
Note:Archived packages are excluded from all counts in the summary bar.
  • The leftmost number represents the total number of active (non-archived) packages under the Package Group
  • ❌ Red cross indicates the number of packages failed on last run
  • ⏸️ Gray Pause symbol indicates the number of packages stopped on last run
  • ✅ Green tick indicates number of packages completed on last run.
This is useful when the packages run regularly (for example, on an Integrate.io ETL schedule). The summary bar shows at a glance whether every job succeeded on the last run, or whether a package failed.
Last modified on October 30, 2026