Help signing in
GreyRow control uses your password and then a six-digit code from your authenticator app. There is no emailed reset link for the authenticator — that is deliberate, because this dashboard can approve work and release changes.
Codes keep getting refused
This is almost always more than one GreyRow entry in the authenticator app. Only one of them matches this account. The others still show six-digit codes that look fine and will never be accepted.
- Open your authenticator app and find every entry that mentions GreyRow or GreyRow control.
- If there is more than one, delete all of them — you cannot tell which is current from the codes alone.
- Also check that the phone's time is set automatically; a drifted clock produces refused codes.
- Then ask the GreyRow owner to reset the authenticator (below) and sign in again to set up one clean entry.
Lost phone or authenticator app
Ask the GreyRow owner to reset your authenticator. Once it is reset, sign in with your password as usual. The set-up screen appears by itself — scan the new code once, and keep only that GreyRow control entry.
For the GreyRow owner
Resetting removes only the authenticator factor. It does not change the password, the account, or what the person can see in GreyRow. After a reset, their next sign-in shows the set-up screen so they can enrol one clean entry.
Do the reset in the identity project (Supabase Auth) for this GreyRow control environment. Diagnose first if you can, then remove the MFA factors for that user only. The exact three steps are in the repository at docs/greyrow/operations/AUTHENTICATOR_RESET_RUNBOOK.md.