Enable Hypothesis LMS app to override client feature flags about client HOT 5 CLOSED

Just a note on some agreement about precedence from a call this afternoon.

The plan in the LMS app is that we will use this to switch feature flags on in some LMS instances while they are off for the h user, but we won't support disabling feature flags via this feature once they are turned on for the h user, eg. by turning the feature on for everyone in h.

The rationale is that once we flip the switch to "on for everyone in H", it means that it really is on for everyone, and there isn't a possibility that it has been disabled somewhere, so we don't have to continue to consider that possibility when testing etc.

from client.

I just want to make a comment on the above. This approach makes sense considering we have decided to enable this feature for LMS users first, and for the "public" users later, but in most of the cases we would want to do it the other way around (I assume), enabling new features for public users first.

Just to have this in mind in case we want to re-use this for future features.

Of course, we can take a completely different approach and start enabling them always for LMS users first, as if they were premium early access features for paying customers.

from client.

This approach makes sense considering we have decided to enable this feature for LMS users first, and for the "public" users later, but in most of the cases we would want to do it the other way around (I assume), enabling new features for public users first.

We can still enable for public users first with this approach. There is a checkbox for feature flags in h which allows a feature to be turned on for first party (ie. public) users only. This is separate from the "everyone" checkbox which means first + third-party users.

In fact, for import/export it is still the plan to turn it on for public users first AFAIK.

from client.

We can still enable for public users first with this approach. There is a checkbox for feature flags in h which allows a feature to be turned on for first party (ie. public) users only. This is separate from the "everyone" checkbox which means first + third-party users.

Right, I always forget about the "first party" option. Then I think we are covered 👍🏼

from client.

This is now deployed.

from client.