Issue 898527  has been merged into this issue.

Connecting to the onboarding/donot show to enterprise users bug

For clarification, had this issue existed before with the original FRE flow? or was this a bug that only happens when the new FRE is enabled?

It's a bug that existed with the original FRE flow as well (we still showed it even when SigninAllowed was set to 0). That was tracked in  Issue 898527 .

Thomas merged that issue into this one. Looks like he was hoping we'd be able to take care of both the old FRE and the new FRE in one patch :) The two FREs require different solutions, though; for the old FRE, we just want to suppress the sign-in screen entirely. For the new FRE, we need to update the UI of the first welcome page, since it contains a button that begins the sign-in process, but also contains a button that launches the rest of the FRE. So I think a little more UX thought needs to be put into what to do for the new FRE.

If it doesn't make sense to tackle both the new and old FRE in the same patch, let us know and I can un-dupe  Issue 898527 .

Thanks Eli. If the audience is enterprise user, does it make sense if we just turn off both the old FRE and new FRE if SigninAllowed=0? The new FRE is not designed for enterprise anyway (we are filtering enterprise users out of the launch), and we will have a separate convo with the enterprise team to see how they may leverage the new structure to build a more enterprise specific on-boarding experience. 

Scott, if we want to turn Navi off if SigninAllowed=0, how difficult is it to implement? 

Oh got it. Yeah in that case, we can just always turn off the FRE (old or new) when SigninAllowed=0. Scott, can you do both in the same CL?

Question - does SigninAllowed only apply to enterprise users? because the new FRE flow doesn't get shown to *any* enterprise users, so if that's the case this is already done.

If it's possible for users to *not* be identified as enterprise, and have SigninAllowed=0, then that's another story.

Do we suppress the new FRE flow in newly created profiles for Enterprise users, as well (as opposed to just the overall first run/first profile)?

To answer your question, SigninAllowed should only be set for Enterprise users, I believe. But it's important to make sure that it's not shown on new profile creation, too.

Also, consumers can turn off the "Allow Chrome sign-in" setting, which is essentially equivalent to setting SigninAllowed=0. We should make sure in that case as well that newly created profiles don't show a sign in prompt during the FRE.