Protect what matters – even after you're gone. Make a plan for your digital legacy today.
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 ProvidedHow to change the Category assigned to a record
I like the way 1Password has expanded the Categories available. I also like that when setting up new records, one can choose and existing Category "template". To make using easier, I'd like to change the Category for an existing record from one Category to another without changing the data structure that exists. Is that possible please? 1Password Version: 8.8.0 Extension Version: 2.3.7 OS Version: Windows 10 Browser:_ Chrome
Request: Turn off username guessing in the apps [RESOLVED]
When I go to create a new login, the user name is prefilled with an email address I haven’t used in years. This shouldn’t have any email address, especially when I use Fastmail’s masked emails. I hope this is a bug and not a normal thing. 1Password Version: 8.10.56 Extension Version: Not Provided OS Version: iPad 18.2 and iOS 18.2 Browser: Not Provided
Wildcard implementation in website property of Login Item
website property inside 1Password Login Item is a great feature which helps to automatically detect and auto fill username and password into the form fields. What's great about it and what's already implemented: You can actually create multiple website properties and still any of the matching websites will work You can set the domain to the website property and any subdomain of that domain will work You can set the domain to the website property and any subdirectory of that domain will work However I can give an example from https://www.netlify.com/ (web deployment platform) which won't match with any of the above 3 features. Let's assume I am developing web application and I set my application url as https://some-app.netlify.app. Netlify has a greate feature to customize subdomains based on the different deployment strategies. For example if I am now working on new github branch and I create a PR #100, then Netlify automatically creates new deployment url https://deploy-preview-129--some-app.netlify.app which is not just a subdomain of netlify.app because there can be thousands of app in netlify, however this is slightly different customized subdomain of netlify with some predefined prefix. So what I would I like is implementation of some custom wildcard options for the subdomains like *sub.domain.com where I can have potentially anything in the place of wildcard *. 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser: Not Provided
Start 1Password minimized and locked on boot
On Windows, 1Password currently starts very prominent on boot. When the application opens, it requests to be authenticated, and it always opens the UI. This is very intrusive from my point of view as 1Password is not always needed right away and you must close the window every time. My suggestion is to add an option to allow 1Password to be started in the background, minimized and locked. This has the following advantages: Backwards compatible / No change for users that like the current behavior When option is activated: 1Password starts silent in the background consistent behavior when screen was locked no prompt to authenticate with 1Password on boot no need to close 1Password Window on every boot authenticate when first time needed
