Best way to share passwords with a team

    Keep shared logins in a vault, and hand each one over through a link that burns after one view.

    Step by step

    1. 1

      Put long-lived team logins in a password manager vault

      A credential the whole team uses for months belongs in a shared vault with access by role. That is storage, and no link replaces it.

    2. 2

      Use a one-time link for every hand-off

      A new hire's first login, a contractor's temporary access, a client's admin password: paste it into the creator below and send the link. It is encrypted in your browser and burns after one view.

    3. 3

      Never paste a password into chat or a shared doc

      Chat history is exported and searched; docs keep every version. If someone already pasted one, the LinkPilot Slack app's message shortcut turns it into a secret link so the original can be deleted.

    4. 4

      Give each person their own login where you can

      Shared accounts are sometimes unavoidable. Where the system allows individual logins, use them, so leaving the team means removing one person rather than rotating a password everyone knows.

    5. 5

      Rotate on departures and on a schedule

      When someone leaves, rotate every shared password they knew and send the new ones through one-time links. On Pro the audit timeline shows who opened what and when.

    Send it with a one-time link

    0/10,000 characters

    Passphrase protection is available on Pro ($29/mo). See plans

    Burn after read is always on for anonymous secrets. The link self-destructs after one view.
    Burn after read
    Encrypted in your browser
    Never expires (until read)

    No account needed. Free forever plan.

    How it works

    1. 01

      Paste a password, a key, or a file

      Encrypted in your browser before anything is sent. Burn after read is on for every anonymous secret.

    2. 02

      Send the link

      One URL. The key after the # stays in the browser and never reaches our servers.

    3. 03

      The stored secret is gone

      The first open burns the ciphertext. A second visit, by anyone, meets the destroyed page.

    Browser-side encryption shipped on 29 September 2026. Secrets created before that date were stored as plaintext until they expired, and a file's name, size and type are still visible to us. Read the full security model.

    Share logins with your team: the two-tool answer

    Teams run into trouble when one tool is asked to do both jobs. A vault is built to store and sync credentials across people who keep needing them. A one-time link is built for the moment a credential moves from one person to another. Using the vault for hand-offs means inviting outsiders into it; using chat for hand-offs means copies everywhere. Use each for what it does, and the secure password sharing guide compares the five common methods in detail, with a policy you can copy.

    What a one-time link gives a team

    The password is encrypted on the sender's device with AES-GCM-256, the key stays in the link after the #, and the first reveal destroys the stored copy. A free workspace lets any member create secrets, set an expiry of one hour, 24 hours or seven days, and revoke a link before it is opened. Pro adds a passphrase, a custom expiry and the audit timeline, and covers up to ten team members.

    A short team policy

    Four lines are enough for most teams.

    • Shared logins live in the vault; nowhere else.
    • A password that has to be sent goes through a one-time link, never through chat, email or a doc.
    • Username and password travel by different routes.
    • Rotate shared passwords when anyone leaves and at least every quarter.

    Frequently asked questions

    Pro, $29 a month, adds a passphrase on every secret, a custom expiry date and time, and the audit timeline that records each view, burn and revoke. See plans.

    Related

    All use cases