Share Link Security

Two self-serve controls, a share password and link expiry, that bound who can open a shared work and for how long.

Applies To

Every liveworkspace app

A share link (the Share dialog calls each one a pass) is a capability: anyone holding the URL has its role. That is what makes sharing frictionless, but it also means a link left lying around keeps working. liveknowledge gives you two controls to tighten that up, a password on the knowledgebase and an expiry on each link, plus revoking a link outright. All three live in the Share dialog, and none of them ever stops you, the owner.

Share Password

You can put a single password on a knowledgebase: switch on Password Protection in the Share dialog, type it, and choose Save. Once it is set, anyone opening any share link for that knowledgebase must enter it before they can view, and the password rides along on every later request so their edits stay gated too.

The password is 6 to 256 characters (spaces at either end don't count). A knowledgebase shared to the Community can't have a password while its post is public.

  • One password covers every link on the knowledgebase, embeds included, not one password per link. While a password is set, the live image option is unavailable, because an image can't ask for a password.
  • You always bypass it. The owner is identified directly, so you never get prompted on your own knowledgebase. So are members of the team whose library holds it.
  • Nobody can read it back. liveknowledge stores only a scrambled (hashed) form of the password, so even you see just Password Set. Note it down when you choose it; use Replace or Remove any time.
  • Changing it takes effect at once. Setting or replacing the password sends everyone currently in the knowledgebase through a link back to the password prompt.
  • Guessing is limited. Share-code and password attempts are rate-limited per network (30 a minute), wherever they are tried.

The goal is to stop people guessing or stumbling onto a share URL, not to provide cryptographic protection. See Share Passwords for the full walkthrough.

When you create a pass, the Valid control sets its lifetime, so access ends automatically without you having to remember to revoke it.

ChoiceLifetime
Foreverno expiry (the default)
1 week7 days
1 month30 days
6 months183 days

When a link expires it stops granting access everywhere at once: the share URL, its embed and live image, and the real-time room all behave as if the link were revoked. The expired link does not vanish, though. It moves to the Expired section of the Share dialog, where you can delete it or Extend it for the same lifetime again, counted from now. A link's lifetime can't be changed after it is created. See Share Link Expiry.

Existing live sessions are not force-disconnected at the exact expiry moment; a visitor loses access on their next load or save. To cut someone off instantly, revoke the link instead: revoking disconnects everyone using it straight away.

Use the two together for sensitive work: a password stops casual access, and an expiry bounds how long even the right people keep it. Remember that anyone who can see an embed's page source can see its link.

How this works in 5 other apps

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us