Configuring Features

kickplan is an openfeature org compliant feature flagging system that transparently supports feature entitlements/authorization based on the plan and overrides for the given account unlike many other feature flagging systems, kickplan features are designed to function as long running flags, deeply integrated into your product so they can serve as entitlements when attached to a plan of course, you can also use features as short lived flags for rolling out new functionality, the choice is up to you once you've created a feature and configured it as part of a plan or as an account override, you'll typically access it inside your application by simply resolving the feature within the context of the current user's account here's a short walkthrough on creating a kickplan feature click on features in the sidebar navigation click on create feature select the feature type kickplan supports several types of features boolean returns true or false values string returns a predefined string integer returns a predefined integer object returns a predefined integer for this example, we choose boolean enter in feature details key is a unique string value that identifies the feature name is how the feature is represented throughout kickplan description and long description are customer facing texts that describe the feature, usually used on pricing pages visible in plan comparison matrix controls whether the feature appears on pricing pages variants allow you to set additional values you want to support for this feature finally, click create to save your feature