Networks & Routing

Private groups

Private groups are named clusters of connections within a network. They provide logical organization — grouping related connections together without affecting how those connections route traffic.

What is a private group

A private group is a named container for one or more private connections within a network. Every private connection belongs to exactly one group. Groups let you organize connections by purpose, project, team, or any other criteria that makes sense for your topology.

For example, you might have a network called "Production" with groups named "Translation Pipeline", "Data Ingestion", and "Customer Support" — each containing the relevant agent-to-agent connections for that workflow.

Automatic creation

Groups are created automatically when you create a connection with a group name. You don't create groups separately — you name the group during connection creation, and if a group with that name doesn't exist in the selected network, it is created alongside the connection. Subsequent connections can reference the same group name to join the existing group.

Use consistent, descriptive group names across your connections. When you type a group name that already exists in the selected network, the new connection is added to the existing group rather than creating a duplicate.

Renaming groups

Rename a group from the Network Contents view on the Networks page. Click the rename icon next to the group name, enter the new name, and confirm. The rename applies immediately — the Canvas, manage page, and Networks page all reflect the new name. Connections within the group are unaffected.

Groups on the Canvas

On the Canvas, private groups appear as container nodes that visually enclose their member connections. Each group container displays a lock icon to indicate it is a private group. Connections within the group are shown as solid edges between agent nodes inside the container. You can collapse or expand group containers to manage visual complexity.

Deleting groups

Deleting a private group removes the group and all connections within it. This is a cascading delete — every connection inside the group is permanently removed. The agents themselves are not affected and can be reconnected into other groups.

Deleting a group cascades to all connections inside it. All connection IDs within the group become invalid immediately. Make sure no agents are actively using those connections before deleting the group.

Groups are organizational only

Private groups do not affect routing, permissions, or proxy behavior. They are purely an organizational tool. A connection in Group A routes identically to a connection in Group B — the group name has no effect on how the proxy handles calls. Groups exist to help you organize and visualize your topology, not to control traffic flow.

If you need routing behavior — sending to multiple agents or load-balancing across agents — use broadcast groups or agent pools instead. Private groups are for organization; broadcasts and pools are for routing.

For fan-out routing to multiple agents, see Broadcast groups →