SavveKey browser extension
One-click sign-in from your own SavveKey vault. Available soon in the Chrome, Edge and Firefox stores.
Set it up
- Install it from the Chrome Web Store, Microsoft Edge Add-ons or Firefox Add-ons once it is listed there. It is available soon in the Chrome, Edge and Firefox stores.
- Enter your vault address. Open the extension and choose Accessing. Type the https address of your SavveKey vault, with no path (for example
https://vault.example.com), then sign in with your vault email and master password. Your administrator can set the address for everyone with a managed policy (below); it is then fixed and cannot be changed in the extension. - Set a PIN. Under Settings → Account security turn on Unlock with PIN, so the extension unlocks with a short code instead of the master password.
- Sign in with one click. Open the item’s menu in the extension and choose Sign in, or fill from the extension on the sign-in page.
What one click does
- Fills your user name and password, and presses sign in.
- Adds the authenticator code when the site asks for one, and presses continue.
- Waits while you approve a push on your phone, then carries on.
- Stops when the page does not look the way it was told to expect. It leaves what is filled and shows “SavveKey: this page changed, so finish signing in by hand.”
It signs in only after you click, on https pages, and when the page has exactly one sign-in form. It acts on the address saved in the item, or on the vetted sign-in pages of a built-in recipe (Microsoft 365 and Entra, Google Workspace, the AWS console). A look-alike address gets nothing.
Tip for the AWS console: in the SavveKey item, use your AWS account’s own sign-in address as the web address, not the general AWS sign-in page. It looks like https://123456789012.signin.aws.amazon.com/console, with your 12-digit account number (or your account alias) at the start. You can copy it from the AWS console under IAM → Dashboard → Sign-in URL. With that address, one click signs you straight in to the right account.
One click, where the site allows it
What a sign-in takes with the SavveKey extension, by the way the site signs you in.
| Sign-in method | What SavveKey does | One click? |
|---|---|---|
| User name + password | Fills and submits, including multi-page flows (email, Next, then password) | Yes |
| Password + authenticator (TOTP) code | Fills, submits, generates the code, fills it, submits | Yes, on sites with a sign-in recipe or a clear code field; otherwise one extra click on the code field |
| Passkey kept in the vault (FIDO2/WebAuthn) | Answers the site’s passkey request for the right site only (origin check) | Nearly: the site may ask you to confirm (a vault unlock, PIN or biometric prompt) |
| Passkey on a hardware key or bound to a device | Nothing to fill; the browser or operating system handles it | No: tap the key or use Windows Hello / Touch ID |
| SMS code | Waits on the code page and asks you to type it (optional later: reads the code from an MSP-owned SMS number) | No by default; yes for shared admin accounts on an MSP-owned number |
| Email code | Waits for you (optional later: reads the code from an authorized mailbox) | No by default; yes with mailbox access |
| Microsoft Authenticator push or number match, Duo push | Fills everything up to the push, shows “Approve on your phone” and carries on after | No: a push is approved by a person, by design |
| Hardware key as second factor (YubiKey OTP, FIDO2) | Fills up to the key prompt | No: needs the key and a touch |
For administrators: set the address with a managed policy
The extension reads one managed setting, techsavveServerUrl: the https address of your vault, with no path. Where it is set, people cannot change it.
Edge (Group Policy, registry or Intune): add a string value named techsavveServerUrl under the extension’s key, for example with PowerShell:
New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\<extension id>\policy" -Force
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\<extension id>\policy" -Name techsavveServerUrl -Value "https://vault.example.com"
Chrome: the same, with Google\Chrome in place of Microsoft\Edge. Intune can deliver it as a PowerShell script or a custom profile that sets the same value. On Linux and macOS, put { "3rdparty": { "extensions": { "<extension id>": { "techsavveServerUrl": "https://vault.example.com" } } } } in the browser’s managed policy file. The Admin Guide in your SavveNOC has the same steps.
Vault traffic goes to your own address. Signed sign-in recipes come from updates.techsavve.com, at most once a day. The breached-password check (api.pwnedpasswords.com, first 5 characters of a hash only) and email alias services are contacted only if you use them. No other server is contacted, and nothing is collected. Read the privacy policy.