This message was deleted.

Hi Thang, thanks for the feedback. I agree it's a little hacky to support your use case currently. I think having env-scoped default values is something we could support in the future. My workflow is usually to keep the default value to

off

and then enable it as needed via override rules. So you could start by forcing the value

on

to everyone in the test environment. And then force it on in prod to specific user ids.

Thanks for the quick reply! Yes I can see using a common attribute like

loggedIn

to forcefully turn it on for everyone once the feature is stable in a particular env. That would work quite well with the workflow you describe.

You can also use a force rule without a condition. That essentially acts like a default value since it will match everyone in the environment.

Nice I didn't know that works as well.

A global switch is useful when you discovered a severe defect and turn it off for all envs, a kill switch maybe?