Transport groups

Organise and operate transports together.

Transport groups are named labels that organise your transports. Use them to tidy a long Transports list into sections and to filter it — and, for the Lakeflow Connector, to scope one Databricks access token to a set of tables.

• Optional. A transport with no group is shown under Ungrouped.
• Assign at creation or move later. Pick (or create) a group in the transport wizard, or move a transport to another group from its detail page.
• First-class + rename-safe. A group has a stable id, so renaming it never breaks anything that points at it (including Lakeflow tokens).

Manage groups

Open Transports → Manage groups to create, rename, or delete a group.

• Create — give it a name (unique) and an optional description.
• Rename / edit — changes apply everywhere the group is referenced.
• Delete — the group's transports are detached (they become Ungrouped); the transports themselves are not deleted. Any Lakeflow token issued for the group is revoked.

Assign a group

• In the wizard — on the first step, choose an existing group or type a new name to create one on the fly.
• On a transport — the detail page's Identity card shows the group; use Move to group to change it.

Filter the list

The Transports list has a Group column and a group filter next to the source/destination filters (including an Ungrouped option) so you can quickly narrow to one group's transports.

Groups and the Lakeflow Connector

For the Lakeflow Connector, the group is the unit a Databricks access token is scoped to: one token serves every Lakeflow-sink transport in the group (one Databricks pipeline ingests the whole group's tables). Issue and revoke the token from the group's Lakeflow access card in Manage groups. A Lakeflow transport must belong to a group.