Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Custom aliases and OpenSSH fields for SSH Bookmarks
SSH bookmarks is a great feature - one I was intending on building myself until I found 1Password's docs for it. However, it is missing a couple important features for me to be truly happy with it. I setup aliases for my common SSH hosts, and would like to be able to add these into 1Password. In particular, I want to be able to set custom names for each bookmark. For instance, I SSH to my university's servers typically with `ssh unsw`, not the far longer `ssh zXXXXXXX@loginX.cse.unsw.edu.au`, which is what the bookmark matches on. In addition, some of these bookmarks are for trusted hosts, where I want to enable `ForwardAgent yes` or similar additional OpenSSH options, and being able to use bookmarks to set these across my devices would be extremely helpful. Currently, I have a config file local to each computer that contains something like the following for each host: Host unsw User zXXXXXXX HostName loginX.cse.unsw.edu.au ForwardAgent yes CanonicalizeHostname yes This converts `unsw` to the long form user and host that is matched by the bookmark config. Ideally, these could all be configured via 1Password. A generic syntax for custom OpenSSH options would also solve other missing properties mentioned by others on this forum (e.g. ports).
Ability to use Sign in With ANY type of login
It would be really helpful if there was a way to use the Sign in With option with ANY type of login entry - not just Google, Amazon, X, Microsoft, and a couple of others. If I have entries for various internal resources that all use the same login credentials, it would be nice to point them all to a single login entry and then only have to update that single point to inherently update all of the ones using it.
Feature Request: Show Original Contributor of Items in Shared Family Vaults
Summary Please add a built-in way to display who originally created or contributed an item to a shared vault in 1Password Family. Problem In shared family vaults, it is currently not possible to see who an item originally belongs to once it has been shared. This makes it unclear who owns a specific account, even though the item is visible to everyone in the family. As a workaround, we manually add tags with the name of the person who created or contributed the item. This allows sorting and filtering by owner, but it is manual, error-prone, and easy to forget. Proposed Feature Display non-editable metadata such as: “Contributed by: Name” or “Original owner: Name” This information should remain visible in the item details after sharing or moving an item into a shared family vault. Benefit This makes it easy to understand who an account actually belongs to, even when it is shared for convenience. It improves clarity in family vaults, avoids confusion, and removes the need for manual tagging. Reference Apple Passwords already shows this information for shared items using labels like “Contributed by: Name”, which provides clear ownership at a glance.
1Password Access after Death, Legacy Contacts
I am not planning to die anytime soon, but sometimes things happen. Beyond securing my 1Password details in an Escrow account, or with a lawyer, or in a bank lockbox, does 1Password offer any means of allowing one or more designated member of the 1Password Families account to access the 1Password account in case of the primary owner's passing? Apple now offers the ability to add one or more https://support.apple.com/en-us/102631 so that in case of your untimely demise, an Access Key and a Death Certificate allows Apple to grant the holder of both of these to get a new Apple ID that has access to your Apple ID Account. It may be something 1Password wants to consider, though I realize that reviewing Death Certificates may not be on the high list of priorities for the team! 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser: Not ProvidedHTTP Basic Auth autofill should be capable of filling on load (maybe normal logins too?)
At work, we use a site that relies on an HTTP basic authentication dialog. My colleagues and I need to access this site multiple times a day, every day. Having to open 1Password and manually click “Autofill” each time quickly becomes frustrating, especially since there’s an additional login screen and 2FA on top of that. While I don’t think this should be enabled by default, I do believe the option should at least be available. More generally, this would be a nice QOA improvement regardless of whether HTTP basic auth is involved. If I’m already on a login page after explicitly clicking a button, I don't get why I should still have to manually select my account. Just something to think about 🙂Feature request – native deduplication & merge for credential items
Hello 1Password team, TL;DR: Imports from browsers/other managers create lots of duplicate logins in 1Password. Cleaning them up now is manual, tedious, and risky (easy to delete or overwrite the “real” password or 2FA). 1Password should add a merge/dedup feature where users can select 2+ items and: Default to the most recently updated record for conflicts. Let users override at the field level (password, username, notes, 2FA, etc.). Optional “find possible duplicates” and an undo/archive mechanism would make it safe and powerful. No major password manager offers this today, so this is a chance for 1Password to differentiate and improve user experience. --- I’m a 1Password user and rely on it as my primary password manager. After importing data from other systems, I’ve run into a recurring problem: duplicated credential records for the same account, often with slightly different fields and timestamps. Right now, resolving this is manual and error-prone: I have to visually compare multiple entries for the same site/service. I’m forced to guess which record has the most current password, notes, or 2FA details. I then manually copy fields over, delete old items, and hope I didn’t miss anything. This is exactly the kind of problem software should solve better than humans. What I’m asking for A native deduplication and merge feature that lets a user select two or more credential items and merge them into one, with: Most recently updated record as the default source of truth For any conflicting fields (e.g., password, username, notes), the system should default to the most recently updated item. The user can override this per field before confirming the merge. Field-level conflict resolution UI Side-by-side comparison of the items. Clear indication of which value is newer. Simple controls to choose “keep this value” per field. Safety + auditability Option to archive original items for a period of time or keep an “undo” path. Activity log entry noting that a merge occurred and which items were involved. Bulk assistance (optional, but powerful) A “Find possible duplicates” view based on domain/URL, username, and title similarity. Let users step through suggested merges in a guided flow. Why this matters (for users and for 1Password) From a user’s perspective: Imports from browsers, legacy managers, and old vaults are normal. Duplicates are inevitable. The current manual cleanup is tedious and fragile, especially when 2FA secrets or secure notes are involved. Fear of losing the “real” password discourages cleanup, which leads to messy vaults and lower trust in the manager. From 1Password’s perspective: A robust deduplication/merge feature directly improves data quality and user confidence in the product. It reduces support load from users who are confused about “which item is correct” after migrations or vault consolidations. To my knowledge, no major password manager offers a proper, user-controlled merge workflow like this; it’s an opportunity for 1Password to lead in a very practical, real-world scenario that almost every serious user hits at some point. Summary 1Password already nails security and cross-platform usability. The next logical step—especially as more users consolidate from multiple tools—is helping them safely clean up and normalize their data. A first-class deduplication and merge workflow would solve a real pain point for me and, I suspect, a large portion of your power users. I’d appreciate it if you could pass this request to your product team and let me know if something like this is on your roadmap. Thanks.Bring 'custom trusted browser' feature to Windows
Following on for the various Opera-related requests that are 'solved' with either 'use a supported browser' or 'solved on mac': please bring this feature to Windows. My personal motivation is Chrome's recent neutering of ad blockers, combined with the excessive use of Windows system notifications for feature advertisement by Firefox and Edge, and the pushing of Web3/crypto nonsense in Brave.Merging Duplicates
I know that the general response is to manually do this, but doing this with 1000+ objects is impractical to say the least. Some were created because when I migrated to 1Password, some duplicate/corrupt entries already existed in my profiles on Avast, Google, etc, which I did not notice at the time. Unfortunately, some have been created since then by either less tech-savvy family members on their own accounts or how 1Password is asking more often regarding site/app trust & permissions ("Allow fill once") and is thus creating duplicates of its own accord. The fact that merging wasn't already added a while back, considering how many people have asked about it over the years, is interesting to say the least. And yes, I have been attempting to create my own tool for quite some time, but it is difficult to find time to work on it lately, on top of not being successful in general.
Inconsistent Searching Between Platforms
Apologies if this is not in the right format or if I'm missing a formality. I did not notice a sticky post detailing proper introductions for new posters. We have an employee migrating from KeePass to 1Password as part of our organization-wide adoption. Unfortunately, they have encountered some issues with the 1Password extension that I was unable to resolve. Similar problems have been reported in other tickets, but, based on my observations, these issues are not correlated across the different 1Password platforms. Core Issues: In KeePass, users could search for strings found in any field, including URLs, notes, and other metadata. In 1Password, however, search functionality only locates entries if the string is in the title, and does not search within other fields such as URLs, notes, or custom fields. This limitation significantly reduces the ability to efficiently locate entries, especially as the number of passwords, links, and other credentials grows. After migrating from KeePass to 1Password, links that previously appeared clickable in the Note field are now displayed as plain text and cannot be directly accessed by clicking. It is worth noting that the user is currently working exclusively with the extension. I have tested this on the desktop application and the web console and can confirm that the search functionality works differently on both platforms. This inconsistency between the extension and the desktop application is causing frustration among our users. With that being said, I’d like to request consistent search functionality across all platforms. This would make it much easier for users to locate information and ensure a smoother transition from other password managers like KeePass. Thank you.
Hardware Category
I like using categories in 1Password but would really like if they added a way to add your own categories or make one for hardware that isn't a router or server. For example i have several things such as laptops, desktops, tablets, smart water controllers, etc. and it would be nice to have a category for things that are password protected. If there is a way to do any of this please let me know.