Two-factor authentication adds a one-time code to your Uptimia sign-in, so a stolen password on its own is not enough to get in. The code comes from an authenticator app on your phone or arrives by email; there is no hardware key and no SMS option. Each identity carries its own setting: you turn it on for your own seat, the code belongs to that seat, and turning it on as the account owner leaves every team member's sign-in exactly as it was.
Before You Start #
- Two-factor authentication is available on every plan and to every role, including a Read-only and an Accounting / Billing seat.
- For the authenticator app you need an app such as Google Authenticator, Microsoft Authenticator, Authy, 1Password or Bitwarden. For email codes you need working access to the mailbox on the identity that signs in.
- Turning it off requires your current password. A Google or GitHub account that has never set a password is exempt.
How the Factor Works #
When two-factor authentication is on for your identity, signing in happens in two stages: you enter your email and password as usual, and only then does the code step start. Uptimia holds you on a verification page and keeps the sign-in pending until you type a 6-digit code in. Until then you are not signed in.
There are two methods, and an identity uses one at a time:
| Method | Where the code comes from | If you lose it |
|---|---|---|
| Authenticator app | A new 6-digit code every 30 seconds in the app on your phone. Nothing is emailed | One of your 10 single-use recovery codes |
| Email codes | A 6-digit code emailed at each sign-in | The Owner or an Admin resets a member; the owner contacts support |
The factor is stored on the identity that signs in, one setting per identity:
| Who is signing in | Whose setting decides | Where the code is sent |
|---|---|---|
| The account owner | The owner's own setting | The owner's authenticator app, or the owner's account email |
| A team member (any role) | That member's own setting | That member's own authenticator app, or their own email address |
An owner with two-factor authentication on and three members with it off means one protected sign-in and three unprotected ones. Each member has to turn it on themselves.
Turning Two-Factor Authentication On #
Open the avatar menu (top right), click Settings, then open the Security tab. With the factor off, the Two-Factor Authentication card shows Status: Off and two buttons.
With an authenticator app #
- Click Set up authenticator app.
- Scan the QR code with your app. If you cannot scan it, click Can't scan it? Enter the key instead and type the key; the type is time-based. Click Next.
- Enter the 6-digit code the app now shows for Uptimia and your Current password, then click Verify and turn on.
- Save the 10 recovery codes with Download .txt or by copying them, tick I saved these codes somewhere safe, and click Done.
The recovery codes are shown once and never again. Turning the app on also signs your other browsers out. If your identity has API keys, the Also revoke box (ticked by default) revokes them too, because an API key never asks for a code. Apps and integrations that use them then need a new key. The setup must be confirmed within 15 minutes; after that, remove the old Uptimia entry from your app and scan the new QR code.
The status then reads Authenticator app with the date it was turned on, and the card shows how many recovery codes you have left.
With email codes #
Click Use email codes instead. An Email codes turned on confirmation appears and the status reads Email codes. Enabling email codes asks for no password. Every later sign-in with that identity goes through the code step.
You can move from email codes to the app at any time with Switch to authenticator app.
Recovery Codes #
Recovery codes exist only with the authenticator app. Each one signs you in once when you do not have your phone. The card under Settings → Security offers three actions:
- Regenerate recovery codes creates 10 new codes and stops every old one, used or not. It asks for your password and a code from the app; a recovery code is not accepted here.
- Move to a new phone replaces the app with a new one. It accepts a code from the current app or a recovery code, and gives you a new set of recovery codes.
- Remove authenticator app is covered under Turning Two-Factor Authentication Off.
When 3 or fewer codes remain, the card shows a Recovery codes: N left warning. After you sign in with a recovery code, that session can move to a new phone, regenerate codes or remove the app for the next 30 minutes without entering another code; your password is still required.
Signing In With a Code #
After Uptimia accepts your password, you land on the code page. With email codes it is headed Enter your security code and reads "We emailed a 6-digit code to the address on your account." Enter the code in Security code and click Verify.
With the authenticator app the page is headed Enter the code from your app. Type the current code into Authentication code and click Verify. Without your phone, click Use a recovery code instead and enter one of your saved codes. Nothing is emailed, so this page has no resend link.
These rules decide what happens on that page.
The code is 6 numeric digits. The field presents a numeric keypad on a phone, so an app or email code never contains a letter. A recovery code has the form xxxxx-xxxxx.
Whitespace is stripped, wherever it falls. A code pasted as 481 502 still verifies, and so does one carrying the trailing space or non-breaking space that webmail adds. For the same reason the field sets no maximum length. Paste it as it came.
You get 5 attempts per sign-in, and Resend code shares them. With email codes, the Didn't get it? Resend code link sends a fresh code and invalidates the previous one, and it leaves the attempt budget where it was, so no amount of resending buys you a sixth try. When the budget is spent, the form closes and the resend link disappears.
Ten wrong codes in a row lock code entry for 15 minutes. This applies to the authenticator app, counts wrong app codes and wrong recovery codes together, and runs across sign-ins. During the lock, a recovery code still works. Uptimia emails you a Several incorrect sign-in codes notice with the IP address the codes came from.
The pending sign-in lasts 1 hour. Mail servers that greylist routinely delay a first delivery by 15 to 60 minutes, and a late code still has to work.
Read the message on screen rather than asking for another code. The failures mean different things:
| Message | What it means | What to do |
|---|---|---|
| That code is incorrect. Check the newest email. (with the app: That code is incorrect. Enter the current code from your app.) | Wrong code, and you have attempts left | Re-enter it. With email codes you can also use Resend code |
| That recovery code doesn't match, or it was already used. | Each recovery code works once | Use another unused recovery code |
| That code was already used. Wait for the next code in your app. | An app code signs in only once | Wait up to 30 seconds for the app's next code |
| Too many incorrect codes | The 5 attempts for this sign-in are spent | Start a fresh sign-in; resending cannot revive it. The same message on the fresh sign-in means you hit the separate ceiling of 30 two-factor requests per 15 minutes from one IP address. Wait 15 minutes, then try again |
| Code entry is locked | 10 wrong app or recovery codes in a row | Wait 15 minutes, or click Use a recovery code |
| Your sign-in timed out | The 1-hour pending sign-in lapsed | Start a fresh sign-in; the code was not the problem |
Turning Two-Factor Authentication Off #
Uptimia treats disabling as a security downgrade, so it asks for your password.
Email codes #
- Open the avatar menu (top right) → Settings, then the Security tab.
- In the Two-Factor Authentication card, click Turn off. A Current Password field appears, hinted "Confirm your password to turn off two-factor authentication."
- Enter your current password.
- Click Turn off two-factor authentication. A Two-factor authentication turned off confirmation appears.
If you leave the field empty, nothing is saved: the page answers Enter your current password to turn off two-factor authentication. A password that does not match returns Incorrect or missing password. Two-factor authentication was not turned off., and the factor stays on.
Authenticator app #
Click Remove authenticator app. Under After removing it, choose Switch to email codes or Turn two-factor authentication off, enter your current password and a code from your app or a recovery code, then click Remove app. The app and all recovery codes stop working for Uptimia.
An account created through Google or GitHub that has never set a password never sees the password field. There is nothing to confirm against. If you would rather have that confirmation, set a password first from the Change Password card on the same page.
The Confirmation Email #
Uptimia emails the identity that made the change, on and off alike. For email codes the subject is Two-factor authentication enabled or Two-factor authentication disabled. The authenticator app has its own notices: Authenticator app two-factor authentication turned on, Your authenticator app was replaced, Authenticator app removed from your account, New recovery codes created and A recovery code was used to sign in. None of them contains a code. The body ends with a line telling you to contact support if you did not make the change.
Warning: An unexpected Two-factor authentication disabled or Authenticator app removed from your account email means someone else is in your account. Change your password immediately. See Securing a Lost Device.
Checking Your Recent Sign-ins #
Below the two-factor card, the Recent sign-ins card lists your own last 10 sign-ins and failed attempts from the past 90 days, including wrong two-factor codes. Each row shows the browser, an approximate location, how you signed in and when. The sign-in you are using now is marked This device, and a failed attempt shows Failed: with the reason. The card is read-only. If a row is not you, change your password.
Two-Factor Authentication for Team Members #
Every seat manages its own factor from the same place: the avatar menu (top right) → Settings → Security tab. On a team member's seat the card's subtitle reads "Add an extra layer of security to your sign-in." rather than "to your account". Members can use the authenticator app or email codes, the same as the owner.
A member cannot change anyone else's factor. Every Security page reaches one identity's setting: the one signed in.
A member's codes belong to their own seat. A member who loses their phone and recovery codes, or the mailbox for email codes, is locked out of their own seat, while the rest of the account signs in as usual.
The Owner and Admins can see who has the factor on: on People → Users the status under Active reads 2FA on or 2FA off. Sign-ins and two-factor changes for the whole account are listed in the Audit Log under the Sign-in & 2FA tab.
Resetting a Locked-Out Member's Factor #
The account Owner and any Admin can clear a member's factor without contacting support:
- Go to People → Users.
- Open the kebab menu on the member's row.
- Click Reset two-factor auth.
The item appears only for an activated member who has the factor on, never on your own row or the owner's. Uptimia turns the member's factor off, removes their authenticator app and recovery codes, emails them that it happened, and logs it in the Recent access changes card on the same page. The member then signs in with their password alone and can enroll again.
No one else on the account can clear the owner's factor. An owner on the authenticator app signs in with a recovery code; an owner who has lost the phone and the recovery codes, or the mailbox for email codes, has to reach support from the email address on the account. Account and Login Recovery covers that path.
Anything on this page can also be done from a script; see Getting Started with the Uptimia API.
What Uptimia's Two-Factor Authentication Does Not Include #
The second factor is an authenticator app (time-based codes) or email. Hardware security keys, passkeys, SMS codes, and SAML or single sign-on are not supported. Email codes have no recovery codes: a member recovers when the Owner or an Admin uses Reset two-factor auth on their row, and the owner recovers through support.
Email codes are exactly as strong as the mailbox they deliver to, so if you use them, protect that mailbox with its own second factor. An authenticator app works without email and is harder to intercept.