Passkeys are a modern way to sign in to Atera using your device instead of a password. Rather than typing credentials, you confirm your identity using your device’s built-in security, such as fingerprint, face recognition, or a PIN.
A passkey is saved securely on your device and works only with your Atera account. When you sign in, your device proves it’s really you, without sending passwords over the internet.
Prerequisites
Before you begin, ensure you meet these requirements:
Supported Device: A computer or mobile device with Windows Hello, Apple Touch ID/Face ID, or a mobile biometric sensor.
2FA Enabled: You must have a standard Authenticator App (TOTP) already configured for the initial setup.
Browser Settings: Use a standard window (avoid Incognito/InPrivate) and ensure pop-ups are allowed for app.atera.com.
Passkey Types & Where They "Live"
Where your passkey is stored determines if you can reuse it across different browsers and devices.
Device-Bound (Platform) Passkeys
Examples: Windows Hello, macOS Touch ID, iCloud Keychain.
They are stored in the OS secure enclave. These are synced only within the same ecosystem (Apple to Apple, Google to Google).
Example: Creating a passkey on a MacBook in Safari means it will work in Chrome and Firefox on that exact same Mac, and on an iPhone signed into the same Apple ID. It will not work on a Windows computer.
Same device, different browser: Yes
Different device, same OS account: Usually (via cloud sync)
Different OS / ecosystem: No
Different browser on different device: No
USB Hardware Security Keys
Examples: YubiKey, Google Titan.
They are stored on the hardware key itself. This is the most portable and ecosystem-neutral option.
Any browser on same device: Yes
Any device (Windows/Mac/Linux): Yes
Any OS: Yes
Without the USB key present: No
Logging in with a USB Security Key
1. Initiate Passkey Login: On the main Atera Welcome screen, instead of entering your email, click the Continue with a passkey button located at the bottom of the form.
2. Select Security Key: A Windows Security window will appear asking you to choose a passkey. Select Security key from the list of options.
3. Authenticate with Your USB Device: Follow the on-screen Windows Security prompts to verify your identity:
You will be prompted to insert and touch your security key.
Enter your security key PIN when prompted and click OK.
You may be asked to touch your security key one more time to complete the verification.
Mobile Phone (Phone-as-Authenticator)
Example: Using your iPhone or Android to scan a QR code on your PC.
They are stored on the phone’s secure storage. This allows you to log in on a desktop that doesn't have its own biometric hardware.
Same phone: Yes
Login on laptop via QR: Yes
Different laptop/browser: Yes
Phone lost: No (unless backed up)
Creating Your Passkey
1. Log in to Atera: Enter your email and password. If you haven't already, you will be prompted to set up your Two-Factor Authentication (2FA) by scanning a QR code, entering the 6-digit code, and saving your recovery code.
2. Start Device Enrollment: After successfully logging in, a Log In Faster on This Device prompt will appear. Click Continue to start the process.
3. Initial Registration & Authentication: Depending on your setup, a system prompt (like Google Password Manager or Windows Hello) will ask where you'd like to save your passkey. Follow the Windows Security prompt to verify your identity by scanning your fingerprint or entering a PIN.
4. Confirm Device Registration: Once verified, you will see a Device registration successful screen. A default device name is provided, but you can rename it in the text box for easy tracking. Click Continue.
5. Initiate Passkey Creation: You will then see a screen offering to Create a passkey for Atera on this device. Click the Create a passkey button.
Note: If you prefer not to set up a passkey immediately, you can bypass this step. Click Continue without passkeys at the bottom of the screen. Note that you will be prompted to enroll again the next time you log in.
Snooze the prompt: To stop seeing the enrollment screen during future logins, check the Don't show me this again box before clicking Continue without passkeys. Clicking “Do not show” on the Create a passkey screen snoozes the prompt for 30 days
6. Confirm Passkey Save Location: A Windows Security window will pop up confirming where your passkey will be saved. If you need to select a different location or authenticator, click the Change button.
7. Final Identity Verification: Follow the final Windows Security prompt to verify it's you by scanning your finger on the fingerprint reader. If you prefer a different method, click Sign-in options.
Logging In With an Existing Passkey (Edge Example)
Once you have successfully registered a passkey, your future logins will be much faster. Here is an example of a successful login with an existing passkey on Edge:
On the Atera login screen, enter your email address and click the Continue with a passkey button at the bottom.
A Windows Security window will appear. Select your Atera account from the list of saved passkeys.
Verify your identity using your device's biometric security. Depending on your hardware, you will be prompted to either scan your fingerprint or use facial recognition.
Once verified, you will be immediately logged into your Atera account without needing to type a password or check your authenticator app!
Troubleshooting Common Issues
Here are the most common situations where your passkey might not work. Because passkeys are synced only within the same ecosystem, switching between different devices or browsers is the most frequent cause of login issues.
"No passkeys available"
This occurs if you click "Continue with a passkey" on a device or browser where you haven't registered one yet. Use your password/2FA to log in first, then follow the enrollment steps.
"Something went wrong" (Storage Mismatch)
A common scenario occurs when a user creates a passkey in Chrome and saves it to the Google Password Manager. When attempting to log in using Firefox or Edge on the same device, authentication fails because Google’s cloud vault is exclusive to the Chrome ecosystem.
For cross-browser compatibility on the same device, ensure Windows Hello or iCloud Keychain is enabled in your browser’s internal settings, registering the credential as a Platform Passkey instead of a browser-specific cloud option.
Lost Devices
Because passkeys are often device-bound, losing a device may lock you out of that specific login method. Always keep your standard Authenticator App (2FA) active as a backup.
