Feature Request: share sensitive data from non-1Password user to 1Password user
I propose a feature enabling 1Password users to securely request and receive sensitive data from non-1Password users via a personalized, one-time link. This link would allow non-1Password users to safely upload and share sensitive information (such as credentials, authentication tokens, etc.) directly with the 1Password user, without requiring them to create a 1Password account.
This feature addresses a common use case of sharing sensitive information that may otherwise occur through insecure channels. By streamlining and securing this process, 1Password could offer a native alternative to tools like PrivateBin, reducing the need for insecure ad hoc methods, saving both time and money.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Comments
-
Thanks for reaching out! If you're using a 1Password Families, Teams or Business membership then you can invite someone as guest and they'll be able to send you documents and other information by uploading them to a shared vault:
Let me know if that doesn't fit your needs.
-Dave
0 -
Hi Dave, appreciate the followup and guidance towards existing features, however, this doesn't quite fit the use case. I'd like something much quicker and more ephemeral without the need for an invite flow.
I'd like to be able to share a one-time link for a user to drop one entry into the vault. I don't even want to create the possibility of a guest user being erroneously promoted to a team member and I don't want to worry about removing the guest after they've shared the vault entry.
Maybe the existing infra around guests can support this use case but without the extra step on the receivers end to have to setup a guest account.
0 -
FWIW - I created this open source project to pull together my different wishlist items, if y'all would like to draw any inspiration https://github.com/osbytes/crypt.fyi
While it is nice for my own personal use, learning, etc. it's less viable in my existing org where we already use 1Password and would be excited if this feature were natively supported.
Anyway, appreciate you passing it along to the team!0