#1Password's SSO implementation, which we're using at work to integrate 1Password login with Okta, is immature and has a lot of UX issues. Generally speaking, it does not appear to be particularly robust from a UX point of view (I have no reason to doubt it's robustness security-wise).

For example: if you try to log into #1Password via SSO on a new device, it's supposed to display a prompt on existing devices to approve the login. However, if you have a linked personal account that's unlocked while your work account is locked, you won't see the prompt or any instructions for how to retrieve it until it occurs to you to unlock your work account. This is shitty UX.

#1Password is integrated with only one email masking service, Fastmail. In contrast, Bitwarden has integrations with numerous services, including the one I use, #Addyio. Until 1Password gets around to adding an integration with Addy.io (which I'm not holding my breath for; people have been asking for this for a while), I guess I have to use the separate Addy.io extension for this. Definitely not a great UX.

There's no way to tell the #1Password browser extension not to prompt to save passwords on a particular website. Again, I'm not holding my breath that they're going to fix this any time soon because people have been asking for it for a long time. This is another area where 1Password lags behind Bitwarden.

Significant bug: the #1Password CLI allows you to retrieve items as JSON using the item title or unique ID. You're supposed to be able to then edit it and upload the edited JSON via the CLI to save the changes. However, when you retrieve an item from your "Private" vault using its title instead of its ID, the resulting JSON file calls the vault "Personal" rather than "Private", and then when you try to upload the changes the JSON is rejected because of the vault name mismatch.

The #1Password desktop app has robust export functionality, which I'm pretty sure is new since my last stint using 1Password. Good for them for adding this! Data portability is important.
Unfortunately, it's only available in the app, not in the browser extension or on the website.
More unfortunately (significant bug), it doesn't appear to work on Linux. The export command is there, but when I enter my password and click the button to do the export, nothing happens.
It works fine on macOS.

Another bug:
The #1Password browser extension is supposed to integrate with the app, so that e.g. you can unlock the extension by unlocking the app and when you ask the extension to edit the item it opens it for editing in the app automatically.
This works fine for me on macOS. It does not work on Linux. Support claims it's supposed to work but hasn't yet told me how to fix it. We'll see if/when they are able to address this. It should work out-of-the-box or tell the user why it's not working.

When you change your #1Password password while the desktop app is locked, the next time you go to unlock it you need to enter your _old_ password, but it doesn't tell you this. Bitwarden's behavior is superior and obviously correct: the Bitwarden app logs you out and requires you to log in with your new password.
If you don't use the app for a long time and when you go to use it you can't remember your old password, you have to reset the app using a reset button buried deep in the settings.

Similarly, when you change your #1Password password while the extension is locked, the next time you unlock it has to be with your old password. However, that's not the end of it. At least for me, after I unlocked the extension with my old password, it immediately locked again _and wouldn't accept either my old or new password_.
I had to turn off browser sync to not mess my other browsers, remove the extension, reinstall it, log back in, put all my settings back, and turn browser sync back on.

There is one vault in #1Password Families called "Shared" which is automatically accessible to all family members. It is impossible to create other vaults with that behavior. It should be, since vaults are not just used to manage permissions, they are also used to logically separate items. For example, I would like to be able to create a separate vault called "Streaming", accessible to everyone in our family, with all of our streaming logins in it.
Can't do it. Bad UX.

@jik Unless I'm misunderstanding what you're hoping to achieve, you can approximate the behavior of a shared vault by creating a new vault and then individually granting access permissions to all family members. It's different in that any future new users would need to be added to this vault to gain access (unlike the Shared vault), but otherwise it can serve the same purpose.

@jhatters I'm not sure which part of "*automatically* accessible to all family members" you missed.
I am obviously aware that I can assign people to vaults manually.
As I said, I don't want to have to do that. I want to be able to create a vault which, just like the "Shared" vault, is automatically accessible to every family member, present or future, without my having to add them all to the vault one by one.