States the click-through cannot reach on its own: server failures, lockouts and Cloudflare Access. Each frame is the real component in that state. Wording follows Nova and Fortify where the screen is theirs.
Loading feature flags…
Could not load the feature flags.
3 people get the Cashbook features on their next page load. Everyone else keeps LedgerVault without Cashbook.
The dialog stays open and shows its own error, so the error is not hidden behind it. The buttons stay on the saved state.
Could not add Priya Raman. Nothing changed. Try again.
These credentials do not match our records.
The same text for an unknown email and a wrong password, so the page does not say which emails are admins.
Too many login attempts. Please try again in 58 seconds.
Too many login attempts. Please try again in 42 seconds.
The code step has its own limit, separate from the password step.
The provided two factor recovery code was invalid.
Each recovery code works once. With no code and no phone, a developer runs admin:reset and sends a new one-time link (CAS-2614).
Not a screen: a developer runs these. The new link opens the one-time link page. Every command writes an audit row. All frames: concept “Admin accounts, option 1”.
Sign in · Atas
Get a login code emailed to you
Cloudflare Access stops them first. Its list of emails covers /admin/*, /nova-api/* and /nova-vendor/*. Each admin's email must be on it. Locally, with no Cloudflare, they see the Nova login: the Xero session does not count for the admin guard, even with is_admin.
Frames for states that the click-through cannot reach by clicking: a server that fails, a lockout at either step, a lost recovery code, the admin commands and Cloudflare Access. Everything else (validation errors, the wrong code, no search match, every confirm) can be reached in the click-through itself.