Features / Packs
Feature Packs
A pack is a named bundle of features — "Group features into packs to manage them collectively across plans." Instead of repeating the same plan or targeting rule across five features, you write it once against the pack and every member inherits it. Composition is per-environment.
Create and fill a pack
1
New pack
Click + New Pack, give it a name (e.g.
premium, core), and create it.2
Add features
Click + on the pack card → search, tick features (Select all supported), and add them. A feature can belong to more than one pack.
3
Remove or delete
Remove a feature with the ✕ on its chip. Delete the pack to remove the grouping — the underlying features stay in the Registry.
What a pack does for you
- In Plans, packs appear in their own section at the top of the matrix — a rule on a pack applies to every feature in it.
- In Targeting, you can target a pack (by plan or by user) so the whole bundle resolves together.
- A direct rule on an individual feature still takes precedence over the rule it would inherit from a pack — useful for one-off exceptions.
Packs are an override grouping, not a status. They're most useful for features in
targeted mode, where a single pack rule decides visibility for the bundle.Per-environment composition
A pack's membership is per-environment — you're editing the pack in whichever of Test / Live is selected. Packs are matched across environments by name, so Promote can create the pack in Live and carry its memberships — including empty packs, via the Packs section of the Promote summary.