Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
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 Provided
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
MacOS Native integration roadmap
Hey 1password ! Thanks for the app it's a pleasure to use in iOS ! Not so much on MacOS platforms due to lack of native integration. I find that more and more of my passwords ends up getting generated and stored in the apple Passwords app simply because 1password isn't an autofill option when I register to a new website. Is native macos integration in the work or on the roadmap ? Thanks !Suggestion: Rich Icons from URL
It would be great if we could add icons to items with a URL instead of uploading the file. Sometimes when I create an item, the URL doesn't have a rich icon. The option to add the icon via upload is okay ("Choose new icon..." but would be a great functionality to add via a URL to the icon.
Request: Bidirectional related items
Current UI: I create a credential (example here: a link to an API feed). I decide to create the API key for it as a related item. That works nicely! When I click into the first credential, I can now see the second: However, when I click into the related item, I can't see .... the other side of the relationship/association: Feature request/idea/suggestion: Related items are automatically bidirectional unless the user specifies otherwise. For items with multiple relations ... perhaps a child/parent architecture could be considered. This would make it easier to navigate betwen related credentials.
