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

Ben, thank you very much for your reply. Too bad it is so difficult to have it what will keep me using LastPass and dropping 1Password that is far better than LastPass. I hope 1password is able to implement something in the very near future so that I can go back to use it.
Again, thanks for the prompt support and sorry for not being able to continue to use 1pass. Ah, the simple availability of independent vaults passwords would also cover the problem if we could keep alternate vaults open or close to access depending on the need.
Cheers
Speed

At present the quickest way to access multiple accounts that have different account passwords would be through Windows Hello (Windows) or Touch ID (Mac). Similar options are also available for Linux.

Ben

I posted two straight questions regarding two accounts with different master passwords and got a quick reply that referred me to this thread. The answer didn't help me as the thread is too long and with too many issues so, I'm sorry, I need to request your help in answering the following and I will really be grateful if someone can help.

I have a family account with 4 sub-accounts. Two of those sub-accounts are mine (private) and I want to access both but with different master passwords.

a) can i use both with this type (family account)?

b) I tried and when I want to switch to the other account it is asking for the Secret Key. Will I need it every time I switch accounts? Is there a way to bypass if this (request secret key) is true?

PS: I'm using version 8 of 1password.

Thanks

Speed

What about the idea of a device specific PIN to unlock all of your vaults regardless of their passwords?

@jpgoldberg What about the idea of device specific PIN codes or passwords?

There's got to be some kind of actual solution to this other than your (admittedly) clunky somewhat non-solution. And I don't think it is necessarily your place to say what an individual account can be used for. Shouldn't that be up to the individuals?

It appears that I failed to read to read carefully enough what people have written, I apologize for that.

Sharing an account password?

If I understand correctly (and I may still be failing to understand), some of you have a workflow in which you actually share account passwords with some clients. That is, you may be consulting for Alice and fully managing her account to the point where you, the consultant, has Alice's account password. Naturally, you would want to unlock a whole bunch of such accounts at once, but you don't want to let Alice have your account passwords for your other accounts,

If that is what is going on (for some of you) then, yes, the new system really does break that workflow, and badly. It is easy for me to say that you shouldn't have a shared account password (and I do say that), but when a client just asks you to take care of things and doesn't want to deal with anything more complicated for them, you are kind of stuck.

Possible work-around

I think that there is a work-around, but it isn't pretty. On the other hand, having two people use the same account password is inherently ugly anyway. The work around is also more expensive. (This isn't some plot to get your clients to send us more money, but it may have that consequence.)

Each of your clients need to have their membership in a non-Individual account. Individual accounts are simply not set up for sharing. Whether that is a team that you are the owner of, or whether you direct your clients to set up a non-individual account will probably depend on your client's needs. But let's suppose it is a separate account "owned" by Alice, even though you set everything up. You make yourself a co-owner of Alice's account. And you create your own membership on her account. You then set up a shared vault (or several) on that account between you and Alice. Alice keeps her own individual account password (although you will know it, you will rarely need it beyond setup). For your membership on Alice's team or family you can use the same account password that you use for all of your clients. So you can get all of those vaults to unlock with a single account password of your choosing without giving Alice and other clients a password that is used for anything other than their own account.

Setup is a bit more complicated, and it won't really work if each of your clients only have Individual accounts, but it makes the flow more coherent. There is not going to be a pretty solution to multiple individuals using the same membership, and thus the same account password. But perhaps this work-around will work for you or at least help you come up with solutions that don't go so much against the grain of what Individual accounts are for.

@jpgoldberg Dude, read my above posts and you’ll find your answer.

So maybe have an "App Master Password" for the app itself and we can choose which vaults/accounts the app master password unlocks?

adamjb, can you let me know what that does for you that setting all of the account passwords the same doesn't?

So maybe have an "App Master Password" for the app itself and we can choose which vaults/accounts the app master password unlocks?

@jpgoldberg You've conveniently ignored some of the legitimate points made here (including my example above) about how this change is completely destroying people's work flow, and is in many way completely untenable going forward. Perhaps give users a choice to setup a primary account, and have that password open up the other accounts.

Or, better yet, why not allow users to setup a PIN code for all of their accounts? This PIN code would be device specific, so it wouldn't compromise security. Each account could have their own PIN code, thus forcing the user to enter each PIN individually. Or, you could create the same PIN for all of your accounts, thus allowing you to unlock all of the accounts at once (just like if they all used the same password).

Alas, based on the history of the 1Password 8 development cycle, most legitimate user suggestion have been flat out ignored (i.e. search is still broken, categories are still hidden behind a drop down menu, etc.)