Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Autofill without unlocking vault.
I would like to request a feature that would allow you to autofill without having to unlock the vault. That way you could have your vault secure at all the time, but still get the convenience of autofilling without entering the password and unlocking the entire vault. Right now you have to choose between maximum security and maximum convenience. It would be nice if there was a middle ground.in Chrome how do I disable autofill of Google Wallet items?
I have some passes, loyalty cards, etc. saved in my Google Wallet. Rather annoyingly, some recent change has caused a Wallet autofill menu to start popping up where it is not wanted, specifically, on the Delta login dialog: I cannot figure out how to disable this. If I go to chrome://settings/payments it shows that 1Password is managing auto-fill: I have also looked all over https://wallet.google.com/ and https://payments.google.com/ and related pages and cannot find any setting that would control this; I have tried disabling 1Password in the above dialog just to make sure I can toggle "Save and fill" off but that doesn't help. In fact, the pop-up menu in the first screenshot only appears when 1Password is enabled. If I disable 1P and reload the Delta website then that popup does not appear. This would seem to imply it is either under 1P's direct control, or a result of how 1P interacts in combination with Google Wallet. This is not a critical bug, since the 1P fill button is still clickable, and/or I can fill my DL creds from the 1P toolbar icon, but it is definitely an annoyance to have the loyalty cards popup in my face when I don't actually _ever_ want it to show up (if I want to autofill a loyalty number that badly I will simply create a 1P entry for it, I don't want to pull anything over from Google Wallet; and even though I can see how others might want that feature, (a) it should be toggle-able (b) wouldn't it be better to integrate the autofill into the existing UI elements instead of popping up a completely separate menu?)
Finding Almost Duplicates
Hello All, I support 1Password in our company of mostly Mac computers. (new to it myself, though) We have a user on a Macbook Air who imported passwords three times over the last year. (I'll give him credit. He's trying!) Each import does have a tag with the import date. I want to remove the old duplicated items from his vault. Watchtower does not show any duplicates. My guess, I haven't confirmed yet, that the items are not exact duplicates. Certainly the tags are different. (Hmm, maybe if I delete the tags they would become duplicates?) I don't want to just delete all items with an old tag because I I can't confirm that all the old ones (> 300 items) have new versions. Maybe there's a way to do that? Maybe we export all of them, delete duplicates in Excel, delete all in 1Password, and then import them again? I'm liking this option. When he did the imports, it didn't keep the Titles. It made new Titles with the website+username (I think). Yuck! Screwed up his logins for apps. This brings up a missing feature. When 1Password imports items, it would be good if it recognized the duplicates at that time and then give options on what to do with them, e.g. not import, keep newest, keep oldest, keep both, merge (?). I'm sure there's a feature request site somewhere. Thank you for any advice.
Domain block/allow listing
This has been requested many times by other users, but I'm not sure if any detailed feature requests were made. The current "hide on this page" right-click option is nowhere near sufficient. Users with many different uses cases, both personal and work-related, need to block entire domains from 1password extension features. "Hide on this page" is not sufficient. 1) it is limited to the right-click context menu, which some web applications hijack. 2) it is limited to specific pages, which can be useless in a deep application navigation state. 3) as far as I can tell, there is no way to view or manually edit the list of blocked pages - the settings menu only provides a button for clearing it. At minimum, block autofill and save-suggestions using a domain list which can be added to using a button from the extension menu AND edited manually. User should be able to paste in a list of domains into a text field to quickly configure the blocklist User should be able to add the current domain or page to the blocklist from the extension menu, instead of or in addition to the right-click context menu Blocklist should support at least simple wildcard matching system, eg: *.community* 1password.community 1password.community/category/discuss/* Extended features could include: an allowlist mode toggle that switches to only allowing 1password to work on specific domains example: user sets app to allowlist mode and allows only work-related sites, avoiding saving personal information in work vaults if they visit non-work sites separately configuring features on each site, implemented as having individual block/allowlists for each feature example: on a web application where you enter customer data, maybe you allow filling credentials but block suggesting or saving form information to avoid capturing customer data
German translation issue on Identity
As you can see, selection criteria and texts are in English on German language in Identity item. Could you please correct them? Also, it would be nice if you can add passport details, ID card details, social security numbers (Versicherungsnummer), tax identification number (Steuernummer or Steuerliche Identifikationsnummer), and so on to the Identity item.
Use YubiKey FIDO2 security key to unlock 1Password for macOS desktop app?
Hello 1Password team and community, I am trying to determine whether it is currently possible to use a YubiKey (FIDO2/WebAuthn security key) to unlock the 1Password desktop application on macOS. Or if this is a feature in an upcoming release? I have configured my 1Password account to use my YubiKey FIDO2 hardware security keys as a second factor for signing in on new devices, and that passkey unlock (which could, in theory, use a security key–backed passkey) is still limited and not generally available in the stable macOS client. However, I have not been able to find a recent discussion that clearly addresses using a YubiKey directly as an unlock method for the macOS app. On my Mac (1Password 8 for Mac), under Settings → Security, the available Unlock options are: Unlock using Touch ID Unlock app with Mac password Unlock with device (for N hours) Require account password (after N days) I don’t see any option to configure a security key as part of unlock, and my expectation would be an additional option under “Unlock” for a security key or keys, similar to how Touch ID and device unlock are presented. My questions: Is there any supported way today to use a YubiKey FIDO2 security key to unlock the 1Password desktop app on macOS (either directly, or via a generally available passkey-unlock configuration)? If not, is this capability on the roadmap for standard accounts, and is there any guidance or timeline that can be shared? Are there any current betas or experimental features that already support this on macOS that I should be aware of? Thank you in advance for any clarification. 1Password for Mac 8.11.24 (81124015) macOS 26.1 (25B78)
Spaces / visual separators for IBANs and other long numbers
I've been looking for a solution or workaround to display IBANs with spaces for better readability, but so far without success. Is there any way to customize the available fields? For example: DE10500105174371973442 --> DE10 5001 0517 4371 9734 42 Interestingly, this feature already exists in principle: credit card numbers are automatically shown with spaces that act only as a visual separator and are not copied along with the number. I really hope this functionality will eventually be extended to IBANs. Actually I also miss it for other long sequences of digits, such as membership/customer numbers or phone numbers. Whenever you need to work with a longer number and rely on readability, things become inconvenient. I hope that this will be addressed in future development. In the meantime: Is there’s already a good workaround or customization option available - perhaps something in the developer area?
