The licensing catalogue

The catalogue defines the products, tiers, services and features that licences draw on, and it is editable here rather than in code.

Pet Central and Pavilion both have a free lowest plan that issues no licence key at all — a site on it never asks the hub what it is entitled to. Each tier includes everything below it, so moving a feature down a plan never takes it away from anyone above.

One thing worth knowing before you edit: a saved override here beats the plugin’s own list until you clear it. That is what makes a correct-looking change to the shipped catalogue appear to do nothing.

A feature that is not in the catalogue cannot be licensed, which is what the pending-features queue is for.

Groups decide services, not just display. A feature’s group is how the hub knows which service it belongs to, through the group’s service setting. A feature in a group with no service is granted to every licence for that product, whatever services were bought. That is what “New features” means: a holding pen for keys the hub has been told about but not told where to file. On a product that sells services separately, leaving one there gives it away to everybody.

Since 0.209.0 a plugin can declare the owning service alongside the tier, and keys the hub has never placed are filed by it. Keys that already have a group are never moved, so anything grouped by hand stays that way. The manifest panel’s green tick compares keys and tiers only — it has never had anything to say about grouping, which is why the count of features with no service is printed beside it.