Groups, Labels, and Group Owners
A group is FleetAMP's ownership and configuration boundary. Administrators give it a readable name such as Payment API NL Prod, while FleetAMP maintains an immutable backend identity.
A Collector can belong to only one ownership group. Labels can narrow deployments within that group, but they do not grant access or transfer ownership.
Administrator responsibilities
Administrators create and delete groups, assign owners, manage Collector membership, define editable configuration sections, review approval requests, and manage drift policy. Before deleting a group, reassign or remove its Collectors and resolve active deployments.
Group Owner responsibilities
A Group Owner can work only with groups they own. Within that scope they can inspect Collectors, propose permitted membership changes, edit permitted configuration sections, validate changes, save a version, preview targets, and submit an approval request. They cannot approve their own request or broaden its target outside the group.
Moving a Collector requires authority over both source and destination groups.
Membership
- Explicit membership selects currently unassigned Collectors during group creation or from the membership workspace.
- Dynamic membership uses a wildcard or regular expression for short-lived or frequently rebuilt Collectors.
FleetAMP rejects overlapping enabled ownership rules. Removing a dynamically matched Collector records an exclusion so it is not immediately added back.
See Manage Collector membership for assignment, move, removal, configuration, approval, and recovery behavior.
Labels
Labels narrow a deployment inside an ownership group—for example, release-ring=canary. They do not move a Collector, grant access, or override ownership.
Configuration history
The Create configuration version action lives on the group page. It loads the latest version; editing enables validation and save actions. Collector-level configuration creation is unavailable to prevent unmanaged exceptions.