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
Experiment #3 - Nearby Items
Hi y'all! I can't believe we are already shipping Experiment 3?! This one has a very special place in my heart. This project actually came out of a Hackday we did internally. Everyone was SOOOO excited about it, we wanted to share it with our users to get your feedback. Nearby Items allows you to assign a location to an item. Then, on mobile only for now, we've added a section to the home tab that shows you items that are close to you physically. Pretty awesome, right? The basic hypothesis here is that because people are more and more mobile, the items you need quick access to might be different based on where you are in the world. If your building at work has a door code, we'll show you that when you pull up. If you've got a storage shed, we'll show you the combo to the lock when you arrive. This experiment is our first exploration into physical space. We know we're not "done" but wanted to get early feedback to help shape how this project evolves from here. We're eager to hear your thoughts on Nearby Items. Let us know what you think below in this thread. The primary questions I'm trying to answer are: Does adding a location to an item help you get things done faster and with less friction? Do you see value in continuing to explore physical locations for items in any form? What are the use cases where you think having an item's physical location would be valuable? We have some ideas, but I'm sure there are tons of things we aren't even thinking about. This is a v1. If we continue to work on Nearby Items, what should we add, change, or modify to make it more valuable to you as a user? Does it make sense to also show "nearby items" on Desktop computers? Do you think that the current form of Nearby Items is good enough to ship in the Stable product?
Issue: Account Owner Permissions & Vaults
Firstly, I want to share that this issue/concern was raised by my company's infrastructure leaders and cybersecurity/information security leaders while discussing rolling out 1Password for our global IT teams. Issue/Concern: 1Password account "Owners" have full permission to manage ANY vault and their vault access cannot be restricted. Therefore, they can add and remove themselves or anyone in the organization to any vault, at any time, without any guardrails. Why is this a problem? As many organizations, we have a broad IT department broken out between application teams, security, cloud and on-premise infrastructure teams as well as deskside and helpdesk support. Our IT teams have a separation of duties for operations and security reasons. Therefore, whoever is a 1Password "Owner" should not be able to see highly sensitive passwords, API keys, etc of another team. So if our cybersecurity/infosec team does not have access to make administrative changes to our server infrastructure but they are supposed to manage the access at the highest level for our 1Password account, should they be owners? What if one owner assigns themself to a vault with sensitive passwords that should only be accessible to our server team? What we found 1Password does not provide native email alerts to notify all 1Password Owners/Administrators when an employee is added or removed from a vault. This would be a great feature at least for 1Password Enterprise accounts. There is no ability to remove the "Owners" group from a vault if the "Manage Vault" permission is granted to a different group. (e.g. A group with only the server team managers and/or director) But if an "Owner" can't manage every vault, then what if the non-owner group member(s) lose access to 1Password or leave the organization? Answer: An Owner or other authorized 1Password Administrator recovers their account or the vault is lost permanently with the only option for it to be deleted by an "Owner". -- Yes, an enterprise will need to accept this risk but they should be offered this level of granularity for certain password/credential security use cases! Shared vault credentials and other data are not secure enough for use within our IT teams with the current and only available way of structuring shared vault permissions with "Owners". Shared vaults are useful for non-IT teams for internal team account sharing. (e.g. Marketing, sales and social media teams) Conclusion We do not feel comfortable using 1Password as our exclusive password management solution due to the lack of available permissions that essentially allow the Owner(s) to elevate their shared vault permissions with no available native 1Password platform warnings, alerts or options to implement guardrails. I hope this drives a strong discussion and would be happy to speak to 1Password leadership on this topic in a private meeting as the only available solution is what is outlined in the link below which was also the only recommendation by a 1Password solutions architect. Due to this lack of permission granularity, our IT teams do not feel comfortable using shared vaults. https://www.1password.community/kb/1password-launch-kit/setting-up-1password-for-large-organizations/687
1Password Date Format
Hi, Am I missing something or is there no way to change the date format for date fields in 1Password? I personally find the US format is the least intuitive format known to mankind. All my documents like passports have dates in UK format, which means there is a cognitive overhead of converting them over and the possibility of transposing them incorrectly when I have to fill details in manually for example. I wouldn't even mind if you could choose an ISO format like 2025-04-01, as long as it goes from most - > least significant value or least -> most significant value. I don't see English (UK) as a language option, and not sure if Language changes the localisation, or just the language. If this is not possible could I add it as a feature request? Thanks, Michael
Onboarding experience: too hard
I have used 1P for many years, and it suits my needs as a software engineer nearly perfectly. However I have suggested it to a number of friends, and done the work of getting two distinct types of user up to speed: my partner (1P Families), and as the IT manager at a smallish company (1P Business). I started both a year or more ago, and thought I would share my experiences. tl;dr After a year, people are still struggling to understand 1P, and are still failing to gain the core benefits such as reused passwords. The main challenge my users have faced is how to migrate from whatever they used before ... intentional or not. My partner uses a Mac and iPhone, and has home and work Google accounts. She doesn't really understand that Safari and Chrome are different things, but uses both at work and home. In both cases, she accepted the default password management features, with autofill in chrome, and various flavors of Apple password managers. At any given time, without reconfiguration, all of these PW managers are competing to manage a password, and the result is confusion, and inevitable password resets "just to get in". So, the user ends up with multiple possible passwords saved in multiple places: Google, Apple, and now 1P. The same has been an issue for my co-workers, who are also at varying levels of technical awareness. The first thing I did for my partner, mainly to make her feel confident, was to import all the passwords from Google and Apple PW managers. This turns out to have been a really bad idea, and also, it's really a great deal harder than it should be -- not very well documented, hard to find on the site, and some parts of it didn't seem to work. This is a terrible idea because Google, at least, saves a new password for any different URL it finds, so there can be multiples just for one site. I am not sure about the Apple version, but the result was that we had at least two, often many more saved passwords imported into 1P. Finally, unless these PW managers are turned off, they keep adding their confusion to the mix. Suggestion: build an importer that figures out how to actually migrate to 1P. There may not be APIs that allow this to be automated, but at least you could build a step-by-step process, and a checker that sees the status and warns users. Ideally the tool would merge (or offer to) sites at the same domain, would identify a suitable name for the 1P entry, would retain history (archive) of old logins, and would coach the user through confirming the result on computer and phone. Passkeys and MFA are both great when 1P gets them right. But I am still regularly assaulted with the option to use passkey with my Amazon account, as well as my AWS accounts. The MFA process is kind of klunky
