Feature request: sharing secrets without creating items explicitly

afrisch
afrisch
Community Member
in Business and Teams

The feature that allows sharing items by sending a link (requiring the recipient to validate the email) is so great I'd like to use it to send one-off secrets to external users. Currently, I need to create an item, generate the share link, and then delete the item after it has been retrieved (or after some time). It would be nice to have a more direct workflow in the UI, also reducing the risk of sharing the "wrong" item from a vault.

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

Comments

  • ag_tommy
    ag_tommy
    edited June 14

    I pinged the products team with your idea, @afisch. Thank you for sharing. Do you have any specific thoughts or ideas on the subject that I can pass along? I'm not sure there is more to add other than a better workflow, but I wanted to see if you had any thoughts. I can always add them later if something comes to mind.

    Cheers,

    ref: PB-40504219

  • stuartclowes
    stuartclowes
    Community Member

    I really want this as well.
    Two use cases spring to mind.

    1) We are resetting passwords for staff, e.g. to Office365. We'll create them a temporary password, which they will need to reset. We want to communicate that to them, but not retain it, or leave it lying around in chat or mail.
    2) Similar to above, but we want to reset passwords for customers of our SaaS products. Again, want to share a password, but keep no record of it.

    For both of the above, we may not be talking to the staff member/customer in real-time. So it's vital we don't send passwords via insecure channels, but also vital that we don't retain them.

    At the moment, we are creating an item, sharing it and then immediately deleting it. Helpdesk/Cutomer Service agents are prone to forget the last step when they are under pressure.

    We had this feature in PasswordState. It was called "self-destruct messages" and had a really simple workflow.

    I am really happy to discuss this further as we really want it.

  • ag_tommy
    ag_tommy

    Thanks @stuartclowes

    I've submitted your feedback to the team for additional review.