Groups and tags
Once you are watching more than a couple of apps, a flat list stops being useful. Groups and tags let you organise them without changing anything about how alerts or billing work.
Groups
A group is a name you give a set of apps, for example a client, a team, or a product line. An app belongs to at most one group. The group page shows a roll-up: open alert counts by severity across every app in it, which app is worst, and the most recent upload across the group.
- 1 to 50 characters. Deleting a group ungroups its apps; it does not delete them.
- Set it from the CLI with
--group, from the manifest'sapp.groupfield, or by picking one on the app page. The group is created automatically if it does not exist yet.
Tags
A tag is free text, 1 to 40 characters, and an app can carry up to 20 of them. There is no separate list of tags to manage; the set you can filter by is just whatever tags are in use right now.
- Set them from the CLI with a repeated
--tagflag, from the manifest'sapp.tagsarray, or by editing them on the app page. - Sending
app.tagsin a manifest replaces the app's tags outright, so include the full list each time, not just the new ones.
Setting both at once
npx vibebeacon@latest scan --upload --group "Client work" --tag backend --tag stripeFiltering
The apps list and the alerts list can both be filtered by one group and any number of tags at once, so you can, for example, see every open alert across just the apps tagged backend in one client's group. Once you have three or more apps with no group set, the apps list nudges you to create one.
See also
The full field rules are on the Manifest format page, and every group's endpoint is on the API page.