Two-factor authentication
Two-factor authentication asks for a six-digit code from an app on your phone after your password, so a password that has leaked is not enough on its own to get into your login. It is optional, and each person turns it on for themselves.
Save your recovery codes somewhere that is not your phone. If you lose your phone and your recovery codes, nobody at Proofbell can switch two-factor off for you. That is not a rule we could relax for a convincing enough request: any way for us to turn it off on your behalf would be a way round it for anybody able to impersonate you convincingly, which is exactly the attack it exists to stop. So without your phone or a recovery code, that login cannot be recovered — not by you, and not by us.
What it protects, and what it does not
It protects your login, not the account. Turning it on changes nothing for anybody else on your team, and an administrator cannot turn it on or off for someone else. There is no setting that requires it of everybody — if your business wants that, it is a matter of asking each person to turn it on.
- Turning it on signs you out everywhere else. The browser you turn it on in stays signed in; every other place your login is open — another computer, a phone, or somebody who has your password — is signed out at that moment and has to sign in again, this time with a code. Account settings tells you how many were signed out. If you are turning it on because you think somebody else has your password, reset your password as well: two-factor stops them signing back in, and a new password means the old one is no use to them either.
- API keys are not affected. A key is a separate credential, not a sign-in, so it is never asked for a code. See API and API keys.
What you need
An authenticator app on your phone. Any app that produces time-based six-digit codes works — Google Authenticator, Microsoft Authenticator, 1Password, Authy, Apple Passwords and many others. You do not need a Proofbell app.
There is no text-message or email option. A text can be diverted by somebody who persuades your mobile network to move your number to their SIM, and a code sent by email would arrive in the same inbox as a password reset link, so anybody who could get into that inbox would have both halves.
Turning it on
Open Account settings and scroll to Yours alone at the foot of the page. Under Two-factor authentication, choose Set up. It takes about a minute:
- Your password, again. You are already signed in, but a session left open on a desk must not be enough for somebody to put their own phone on your login and lock you out of it.
- Scan the QR code with your authenticator app. If you cannot scan it, choose "enter a setup key" in the app, name the entry Proofbell, and type the key shown beside the code. If you are doing this on the phone that holds the app, use Open it in your authenticator app instead, since a phone cannot point its camera at its own screen.
- Enter the six-digit code the app shows and choose Turn on.
Nothing changes about signing in until that code is accepted, so an abandoned setup cannot lock you out. If you start and do not finish, Account settings says so next time and offers both ways on: finish with a code from the app if Proofbell is already in it, or start again. Starting again makes a new key, so delete the old Proofbell entry from your app — its codes will never be accepted.
Once the code is accepted you are shown ten recovery codes, once. We store only a scrambled form of them and cannot show them to you again. Use Copy all or Download as .txt, keep them in a password manager or print them and put them away, and tick I have saved these codes somewhere safe to finish.
Signing in
After your password, you are asked for the code from your authenticator app. You are asked only if you have turned two-factor on — everybody else signs in with a password as before. The same box accepts a recovery code; spaces and hyphens do not matter.
You have five minutes to enter the code after your password is accepted. Leave it longer and the page asks you to start again from your password — that is the sign-in timing out, not the code being wrong.
Remember this device for 30 days
The code step has a Remember this device for 30 days checkbox, unticked by default. Tick it and that browser will not ask you for a code for 30 days. It never skips your password. It only skips the code, and only on that one browser.
The 30 days are fixed, counted from the sign-in where you entered the code. Using the browser does not restart or extend them. After 30 days you are asked for a code again, and you can tick the box again then. If each sign-in restarted the clock, a browser that signed in once a month would never be asked for a code again, and two-factor on that browser would have been proved once and then taken on trust for good.
It only works with a code from your authenticator app. If you sign in with a recovery code, the browser is not remembered even with the box ticked, and the sign-in page says so. A recovery code works once, and letting it buy 30 days without codes would turn one leaked recovery code into a second factor that went on working. To remember a browser, sign in with the app.
Do not tick it on a shared or public computer. It would leave that machine one password away from your login.
A remembered browser is forgotten, and will ask for a code again, when any of these happens:
- you turn two-factor off;
- you reset your password;
- you choose Forget remembered devices in Account settings, which forgets every browser at once, including the one you are using — Account settings shows how many there are under Remembered browsers, but not which ones, so this is the way to be sure;
- the browser's cookies are cleared.
If the sign-in page tells you this browser was not remembered, it means what it says: you will be asked for a code next time on that browser.
Recovery codes
A recovery code is ten letters and numbers in two groups of five. Each one signs you in once, in place of a code from your app. When you use one, the sign-in page tells you it will not work again and how many you have left; Account settings shows the count all the time and warns you from three downwards.
New recovery codes in Account settings gives you a fresh set of ten, and the old ones stop working at once. It needs a code from your authenticator app — a recovery code cannot be used to get new ones. Otherwise somebody who had found one of your codes could trade it for ten fresh ones you have never seen.
If you lose your phone
- Sign in with one of your recovery codes.
- In Account settings, choose Turn off and enter another recovery code — the one you signed in with has been used.
- Choose Set up and go through setup again on your new phone. You get ten new recovery codes; the old ones went when you turned it off.
If you have neither your phone nor a recovery code, Proofbell cannot get you back in. There is no support route that switches two-factor off for you, for the reason at the top of this page. Another administrator on your account can invite you again under a different email address, which gives you a new login rather than your old one back — the old login's history stays in the activity log. If nobody else on the account is an administrator, that route does not exist either, which is a good reason to have more than one.
When a code is refused
- "That code has already been used." A code works once, so one that has just signed you in, or was just typed somewhere else, cannot be used again. Wait for your app to show the next one — they change every 30 seconds — and use that.
- Every code is refused. Check that your phone sets its clock automatically. The codes are worked out from the time, and we allow for a clock about thirty seconds out either way — a phone that has drifted further than that produces codes that are wrong when they arrive.
- "Too many attempts. Wait a few minutes and try again." Wrong codes are counted, because a six-digit code could otherwise be guessed. After ten, your login is paused for fifteen minutes.
During that pause, the password step says "Those details did not match an account" — even when your email address and password are right. It is deliberately the same sentence as a wrong password: a different one would tell anybody typing addresses into the sign-in page which ones belong to an account and are being guessed at. Wait fifteen minutes, or reset your password, which clears the pause. A reset does not turn two-factor off — you will still be asked for a code afterwards.
Turning it off
Turn off in Account settings needs a current code from your app or a recovery code. That is so that somebody using a session you left open cannot switch it off and keep your login. Turning it off:
- deletes your recovery codes, so none of them will work again;
- forgets every remembered browser;
- takes signing in back to your password alone.
You can remove the Proofbell entry from your authenticator app afterwards. If you turn it on again later, you start from a new key and a new set of codes.
In the activity log
Six actions are recorded, each with your name, the time and the address it came from:
- turning two-factor on (
user.mfa.enabled); - turning it off (
user.mfa.disabled); - getting new recovery codes (
user.mfa.recovery_codes_regenerated); - forgetting remembered browsers (
user.mfa.trusted_devices_forgotten); - a browser being remembered at sign-in (
user.mfa.device_remembered); -
a sign-in that skipped the code because the browser was remembered
(
user.mfa.trusted_device_sign_in).
The last one is there because that sign-in had one factor fewer than your login is set up for, and after an incident "when was the code skipped, and from where" is the question you will want answered. The log shows each action as a sentence ("Mfa enabled" and so on), with the full name beside it.
An entry is written to every account your login belongs to. If your access covers the whole agency or business rather than particular accounts, the entry belongs to no single account: it appears in the log's agency-wide view, labelled Agency-level, rather than under any one account. Only administrators and agency owners can read the log — see Activity log. No code, key or recovery code is ever written to it.
What is not built
- No team-wide requirement. Nothing can make two-factor compulsory for everyone on an account, and nobody can turn it on or off for somebody else.
- No text-message or email codes, for the reasons above.
- No security keys or passkeys. An authenticator app is the only second factor.
- No single sign-on. You sign in with your email address and password, plus the code if you have turned it on.
- No list of remembered browsers. Account settings shows how many there are and can forget them all at once; it cannot forget just one.