1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-11-24 20:06:55 +01:00

Update docs/user_guide/strategy-constraints.md

Co-authored-by: Christopher Kolstad <chriswk@fastmail.com>
This commit is contained in:
Ivar Conradi Østhus 2021-02-25 09:11:50 +01:00 committed by GitHub
parent aff7d9167d
commit 4e0d732e63
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -17,7 +17,7 @@ The most common use case for strategy constraints is that you want an activation
## Constrain on custom context fields
It is also possible to constrain a activation strategy configuration on custom context fields. A common use case is a multi-tenant service where you want to control roll-out on a tenant identifier. This enable you to decide which customer should get access to your new feature.
It is also possible to constrain a activation strategy configuration on custom context fields. A common use case is a multi-tenant service where you want to control roll-out on a tenant identifier. This allows you to decide which customer should get access to your new feature.
![Custom constraints](../assets/custom-constraints.png)