The Assignments tab

Every Flow, Agent, App, and Suite has an Assignments tab in its editor. It lists every group that can reach the asset, with a type badge, and it is the only place access is written.

The empty state says it plainly: No one can access this asset yet. Assign a group or a plan. Until a row exists here, the asset is unreachable from every Portal. A direct share link to a Flow or Suite is not a Portal and is not gated by this tab.

Adding a row

Open the asset and switch to Assignments.
Click Add assignment and pick one or more groups. The picker lists Assigned groups and Self-Service Plans together. Optionally set an expiry date (the default is Never).
Save. The row appears with the group's type (Assigned or Self-Service), its member or subscriber count, and, for a plan, its price.

Rows are organization-wide: an assignment is not scoped to one Portal. Which Portals show the asset follows from which doors admit the group (see Portals as doors).

Removing a row

Remove the row and the group's members lose the asset on their next visit. For a Self-Service Plan, subscribers keep their subscription and credits - they only lose this asset.

Filtering

Filter the list by type (All, Assigned, Self-Service) to see only the plans that sell an asset, or only the Assigned Groups that get it for free.

What the tab does not do

It does not create groups or plans. Create Assigned Groups under Users & Groups; create plans under Self-Service Plans.
It does not offer plans for sale. That happens on a Storefront.
It does not decide credits. A run is metered against the user's plans when they have one, and against your organization otherwise - see Plans & Credits.

Reading the same picture from the other side

A group's record shows an Assigned to list - every asset it reaches - and links back to each Assignments tab. The two views are the same data, so whichever way you approach a question ("who can use this?" or "what can they use?") you land on an editable row.

The Assignments Tab