📄️ Activation Strategies
It is powerful to be able to turn a feature on and off instantaneously, without redeploying the application. The next level of control comes when you are able to enable a feature for specific users or enable it for a small subset of users. We achieve this level of control with the help of activation strategies. The most straightforward strategy is the standard strategy, which basically means that the feature should be enabled to everyone.
📄️ API tokens and client keys
For Unleash to be of any use, it requires at least a server and a consuming client. More advanced use cases may call for multiple clients, automated feature toggle updates, the Unleash proxy and Unleash proxy clients, and more. To facilitate communication between all these moving parts, Unleash uses a system of API tokens and client keys, all with a specific purpose in mind.
📄️ Archived toggles
You can archive a feature toggle when it is not needed anymore. You do this by clicking the "Archive" button on the feature toggle details view. When you archive a feature toggle, it will no longer be available to Client SDKs.
📄️ The event log
The event log lets you track changes in Unleash. It lists what changed, when it changed, and who performed the change.
📄️ Impression data
The impression data feature was introduced in Unleash 4.7. It is available in the JavaScript-based proxy clients and in some server-side SDKs. Please refer to the SDK compatibility table for an overview of server-side SDKs that support it.
📄️ Custom Activation Strategies
This document is a reference for custom activation strategies. If you're looking for a guide on how to use them, see the how to use custom strategies guide.
📄️ Environments
Environments were released in Unleash v4.3.0.
📄️ Feature Toggles
Feature toggles are the central concept that we built Unleash around. In Unleash, feature toggles are organized within projects. Feature toggles can have different activation strategies for each of their project's environments, and can also be given variants to facilitate A/B testing.
📄️ Feature Toggle Types
This feature was introduced in Unleash v3.5.0.
📄️ Feature Toggle Variants
Feature toggle variants were first introduced in Unleash 3.2.
📄️ Front-end API access
The Unleash front-end API was released in Unleash 4.18. You can read more in the Unleash 4.18 release blog post.
📄️ Login history
Login history is an enterprise feature available from Unleash 4.22 onwards.
📄️ Network view
The network view was released in Unleash 4.21. It is available to Pro and Enterprise users.
📄️ The Playground
The Unleash playground is available from Unleash 4.14 onwards. The playground is available in all Unleash versions.
📄️ Public Invite Links
Public invite links let you invite team members to your Unleash instance. Any user with an invite link can sign up to Unleash instance that created the link. The user will get the viewer role (refer to the standard roles section of the RBAC document for more information on roles).
📄️ Projects
All users get access to projects, but only pro and enterprise users can create, update, or delete them.
📄️ Role-based Access control
This document forms the specifications for Role-Based Access Control which was introduced as part of the Unleash v4 release.
📄️ Segments
Segments are available to Unleash Pro and Unleash Enterprise users since Unleash 4.13.
📄️ Service accounts
Service accounts is an enterprise feature available from Unleash 4.21 onwards.
📄️ Single Sign-On
The Single-Sign-On capability is only available for customers on the Enterprise subscription. Check out the Unleash plans for details.
📄️ Stickiness
Stickiness is how Unleash guarantees that the same user gets the same features every time. Stickiness is useful in any scenario where you want to either show a feature to only a subset of users or give users a variant of a feature.
📄️ Strategy Constraints
Before Unleash 4.16, strategy constraints were only available to Unleash Pro and Enterprise users. From 4.16 onwards, they're available to everyone.
📄️ Tags
This feature was introduced in Unleash 3.11.0
📄️ Technical Debt
At Unleash we care deeply about code quality. Technical debt creeps up over time and slowly builds to the point where it really starts to hurt. At that point it's too late. Feature toggles that have outlived their feature and are not cleaned up represent technical debt that you should remove from your code.
📄️ Unleash Context
The Unleash Context contains information relating to the current feature toggle request. Unleash uses this context to evaluate activation strategies and strategy constraints and to calculate toggle stickiness. The Unleash Context is an important feature of all the Unleash client SDKs.
📄️ Change requests
The change requests feature is an enterprise-only feature that was introduced in Unleash 4.19.0.
📄️ Maintenance Mode
Maintenance mode was introduced in Unleash 4.22.0.