Capabilities to Features

Capabilities are actively being phased out in favour of features. We have spent the last year making a number of key improvements to features, and they’re now at a point where they’re simpler to use, easier to understand, and more flexible than capabilities.

Starting from 3rd July 2025, you will no longer see the “Capabilities” view in any new products you create, or existing products that didn’t already have at least one. Legacy capabilities will continue to exist and function as normal.

In products which still have capabilities active, we would recommend migrating them to features for the additional flexibility, and simpler usage.

One key difference between the two is that capabilities were immutably placed onto a subscription. Once it was there, it couldn’t be removed or tweaked without giving the grantee an entirely new subscription. Features don’t have this problem, you can change feature values and the subscriptions will instantaneously update to reflect the changes.

Turning a capability into a feature

Capabilities were on/off values, something that was either present on a subscription or not. This logic can be represented with a “boolean” feature. Replacing a capability with a feature requires you to create a boolean feature with a similar or the same name. You may have to make slight adjustments to your license checking logic if the capability name and the new features “Variable Name” don’t match.