I built a new strategy that basically lets me toggle whether or not a feature is on for a known set of users (like all employees). This all works fine, but if I'm logged in as a non-employee looking at the feature settings it would show the toggle as "off" because it conflates a flag being on with a flag applying to me. Ideally these would be separate so that I could see the status of a flag as it applies globally and switch it. I realize that this is backwards from how the cookie strategy has to work, since it has local scope, but the api should probably handle the broader case.
I built a new strategy that basically lets me toggle whether or not a feature is on for a known set of users (like all employees). This all works fine, but if I'm logged in as a non-employee looking at the feature settings it would show the toggle as "off" because it conflates a flag being on with a flag applying to me. Ideally these would be separate so that I could see the status of a flag as it applies globally and switch it. I realize that this is backwards from how the cookie strategy has to work, since it has local scope, but the api should probably handle the broader case.