Skip to main content

Manual Groups

FRP Auto Deploy v2.2.1 includes a Manual Group MVP for organizing clients. Groups are administrator metadata: they do not change CLIENT ID, service configuration, public ports, or tunnel behavior.
v2.2.1 supports manual groups only. Dynamic membership rules and large-scale fleet orchestration are outside this stable scope.

Create a group

Each stored group has an immutable group ID such as grp_1234abcd. The name and description can be changed later.

Add a client

Use the client’s canonical CLIENT ID when possible:
A client can belong to more than one group.

View groups and membership

all and ungrouped are virtual selectors; they are not stored group objects.

Rename or describe a group

Changing the group name does not change its immutable group ID.

Remove membership

This only removes the membership relationship. The client remains enrolled and its services and public-port reservations are unchanged.

Delete a group

Deleting a group removes its membership references but does not delete clients, revoke identities, disable services, or release ports.
Group deletion is not a client lifecycle action. Use Lifecycle Semantics for revoke/release decisions.

Typical uses

Manual groups are useful for a small fleet when you want simple operator categories such as:
  • customer or partner
  • branch/site
  • lab vs production-support systems
  • temporary support campaign
For the current project target of roughly 1–50 clients, this keeps client lists easier to navigate without introducing a separate fleet-management platform.
Last modified on September 9, 2026