Hi team, I've been looking at setting up permissive feature flags for our clients. Currently, the only way I can think of doing it, is setting up override rules per feature basis, but that makes things a little messy, as we can have couple hundred rules on some features at some point. Is there a better way to manage that?
• featureA - Override rules for org1 and org2 to set value to enabled
• featureB - override rules for org1, org2, org3...org40
Then we would use attributes to resolve the feature state for org
11/07/2023, 9:41 AM
@rough-solstice-65123 has marked the issue as closed. Reopen Issue button
⭐ Our official support hours are 6:30am - 5pm Pacific Time, Monday through Friday. You may occasionally hear from us outside of these hours.
Your support request has been logged in our system. Our support team will get back to you very soon!
11/07/2023, 2:20 PM
Hi, I’ve got your support request in my queue and I’ll follow up as soon as I can
11/07/2023, 4:05 PM
Question: Is there some logical grouping of organizations or does every org have their own unique set of permissions?
If you are able to group organizations together, Saved Groups can help. For example, you can define an "Enterprise" group with 20 org ids and use that group in the targeting conditions for features. Then, if you need to add or remove a user from the group, every feature that references it will be updated automatically.