Two accounts - now needs two different passwords every time you login?

Hello everyone,

I have been a long time 1Password user, from the standalone vault days, through Dropbox sync and currently use 1password.com.
The service and application has been outstanding up until version 8.

I am still at a loss as to why I cannot unlock multiple vaults using a single password.

I am a user who has multiple separate paid 1password.com accounts setup in my 1Password applications. These are not a family/shared account.

Let's call them John and Mary accounts.

• I have read through these posts and understand the premise of what used to be a "master vault" and the confusion that caused and the technical reason outlined as to why it has to go. I completely agree, and had concerns about this approach when initially using this feature in previous versions.
• I don't think using the same master password across vaults is a good idea, this is a decision by users ultimately, but not a robust long term solution.
• As I see it, the whole idea of 1Password is to (1) improve security, and (2) streamline the "login" experience, be it using an App, a website, or whatever

I fail to understand how there is not a feature and associated UX element which allows me to:
1. Install a 1Password v8 client and initially add/login as John
2. Store the details for Mary's 1Password account in John's account, including email, secret key, master password and 2FA for Mary's account - all formatted correctly
3. Add Mary's account to my 1Password v8 clients, initial setup being completed by manually entering all account info or scanning the QR code
4. Instead of 1Password asking me to unlock Mary's account by manually every subsequent Application restart by entering Mary's master password, it takes the fact I store Mary's account credentials in an already unlocked account and proceeds to unlock Mary's account

To me, this solution embodies the very underpinnings of 1Password - taking complex password information which has been previously securely unlocked and presenting it to applications to fast authentication.

F*@^ing fix it already.