Thank you for taking a moment to send your question.
This is indeed a known issue. If you'd like to have multiple
users logged in simultaneously, and using 1Password, you'll either
have to use different web browsers (this isn't a problem if one is
on Chrome and one Safari, for example), or make sure you quit the
browser before switching users.
Hopefully this is something we'll be able to correct in the
future, tough I don't have a guess right now exactly when that
Please let me know if there's anything else I can help with.
it seems there hasn't been any resolution for this issue yet.
Both my wife and I really love 1Password, but this is by far the
biggest annoyance. We both use the same computer and often switch
back and forth between our accounts. We think it shouldn't be
necessary to quit browsers each time or to log out.
Could you guys please reinvestigate? It seems quite strange that
two users could possibly interfere with each other in that way and
also raises the question whether this could pose a security
Support Staff5 Posted by Kyle Swank on 21 Jun, 2012 01:21 PM
Thanks for taking the time to contact us with your questions.
I'm sorry that this hasn't been fixed. However, it is a lower
priority issue at this time. It's also not an easy fix and will
require some significant rewrites.
There are two workarounds for this issue though:
1) Quit the web browser before switching users. The keyboard
shortcut only ties itself to a particular instance when the browser
is open. If you quit the browser it will release the shortcut and
allow the second user to work fine.
2) Use a different web browser for each user. If one user uses
Safari the other can use Firefox or Chrome. The shortcut is only
tied to a particular browser, so if you each use separate browsers
then you won't have the issue happen.
I realize this is frustrating. I myself am affected because I
use two logins on my computers for work here. One login for
personal and another for work. I use the two browser method and it
works fine for me. Though I'd love to see this issue fixed.
I am sorry for the inconvenience, hopefully it'll get fixed in