We use 1password at our company to protect secrets. It works great. But, some secrets are more sensitive than others. This feature request proposes a strategy to add an extra layer of protection to critical secrets.
Practical example: we have a single "master account" for our cloud tech stack that is placed in a 1password vault with very restricted access. This account was used once upon a time to create the owner accounts for sub-organizations; those accounts, in turn, were used to create accounts with reduced privileges, and so on. Our expectation is that the only reason anyone would need to access the master account is during rare events like tearing down / adding a new division, shutting down access to a compromised admin account, and so forth.
As you can imagine, a compromise of the master account credentials could be catastrophic.
We've considered just taking credentials like this out of 1password entirely and storing them in a physical location, like a bank's safety deposit box. But, this isn't ideal, since in the event of a major breach of an admin account, it could take hours or even days to gain access to the master account.
Our middle-ground suggestion would be the option to mark a vault item as requiring more than 1 user (perhaps from a selected "trusted group" of users) to unlock the item to enable viewing it. This could be thought of as a virtual version of the classic two-man rule where two people people have to turn their keys at the same time to start the nuclear launch sequence
One implementation approach might be to mimic the existing "account recovery" process and chain the access requests:
Thank you for your time!
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided