Core idea: a master password answers “do you know the vault secret?” Trusted-device approval can add a separate question: “does a device already connected to this account accept this new client?”
Why enrollment deserves its own control
For master-device-only approval, only your current master device can approve a new login and receive its approval notification. This choice does not allow email or another device to approve instead.
A synchronized password manager has to decide when a new browser or phone may receive encrypted vault data. If possession of an email address and master password is the only requirement, an attacker who captures both can attempt enrollment from a remote machine.
Trusted-device approval changes that path. The unfamiliar client first creates a pending request with its identity, name, IP address, and available network-location context. A device already associated with the account can inspect and accept or reject the request before enrollment completes.
Choose your approval methods
Another Authier device — recommended
A connected device must approve the pending request. This is convenient when you own several trusted clients because any one of them can help enroll the new browser.
Email — most convenient, least secure
Review and confirm a link sent to your account email. This works without a second Authier device, but anyone who gains access to your mailbox can approve a login. Your master password is still required afterward.
You can enable both methods. Choose “Either approval is enough” for a fallback through email, or “Require both approvals” to require email confirmation and approval from another Authier device. No new device receives the account salt or encrypted enrollment secret until its required approvals are complete.
What approval can stop
- A remote enrollment attempt using a captured account email and master password.
- A silent new-device login when the configured policy requires explicit review.
- Continued access from a device that you later sign out or remove.
- Automatic TOTP synchronization to a device where you have switched that setting off.
What approval cannot stop
- Malware or a malicious extension reading data from an already-unlocked client.
- A user approving a convincing fraudulent request without checking its context.
- Physical access to an unlocked device or compromise of its operating system.
- Implementation flaws in the client, backend, cryptography, or recovery flow.
- Phishing that captures credentials used directly at the target service.
Device approval is defense in depth, not a security guarantee. It should sit beside local device security, a strong master password, encrypted vault storage, careful recovery, and phishing-resistant authentication where available.
Recovery is part of the threat model
Strict approval becomes dangerous if losing one device permanently locks out the owner. Authier includes a recovery-based master-device reset flow with an email confirmation and configurable cooldown. The delay gives an existing owner time to notice and reject a fraudulent recovery attempt, but email security becomes part of the recovery chain.
Recovery controls must balance two failures: unauthorized access and permanent lockout. A longer cooldown gives more detection time; a shorter one restores access sooner. Protect the email account, retain independent recovery methods, and test the process before an emergency.
How to review an approval request
- Initiate enrollment yourself and keep both devices visible.
- Compare the displayed device name, time, IP address, and approximate location.
- Reject any request you cannot explain, even when one detail looks familiar.
- After approval, verify the new client and remove old devices you no longer control.
- Review whether TOTP synchronization and lock timeout are appropriate for that device.
Evidence you can inspect
Authier’s request, approval, recovery, and device-management paths are public in the source repository. The current implementation records approval state, device history, sync state, IP context, and recovery timing. Authier has not published an independent third-party audit, so public code should be treated as inspectable evidence, not proof that the design is flawless.
Continue evaluating: read the exact encryption and security architecture, then compare the broader selection criteria in the browser password manager guide.