@Michael Landolfi I'm realizing it’s possible that a parent could have started onboarding on a version <1.6.2, and if they stuck long enough before rounding their kids devices up they'd download 1.6.2 on their kids devices which wants a QR scan or entered code to link. 1.6.1 doesn't have that. So action if we see this would be sock puppet and tell parent to update their app and that will solve. I'll keep an eye on these cases as well but flagging for on-call