Keep your verified account and support status when you sign in
Signing in holds on to the account state you already had, including email verification, white-glove support marking, and your home organization.
Signing back into Chief used to undo things about your account that were already settled. Your account could slide back to pending verification, a support marking could vanish, or the web app could hold a sign-in token the platform had already replaced. Four fixes now keep that state intact.
Verified accounts stay verified
Signing in with an unverified email dropped a registered account back to pending verification, and every sign-in rewrote your account record. Your account now keeps the status it already had.
White-glove support marking
If you were marked for white-glove support, the next profile sync that changed anything else on your account wiped the mark, with no sign that it happened. The mark now survives later sign-ins.
Personal access tokens for closed accounts
A personal access token belonging to a deleted, deactivated or flagged account could still authenticate. Chief now refuses those tokens.
Home organization after sign-in
When you moved into the app from a marketing page and the platform re-pinned your account to its home organization, the web app kept the older sign-in token and later requests carried the wrong organization. The web app now uses the refreshed token.
You do not need to do anything. Sign in as usual and your account comes back the way you left it.