Link lifecycle

Plan expiry before a shared link escapes

A link can outlive the chat, project and person who created it. Give it an owner and an ending while the context is still fresh.

Lifecycle rule: every shared link should have a purpose, owner, access model, review date and defined behaviour after retirement.

Expiry, deletion and revocation differ

Expiry usually means a service stops honouring a link after a date. Revocation means an owner disables access sooner. Deletion may remove the underlying object from active storage. These states are often presented as one button, but they answer different questions.

A revoked link does not erase downloaded copies. A deleted object may remain in backups. An expired link may still expose a filename or preview. Read the service documentation and test the exact behaviour in a private browser before relying on it.

Match lifetime to context

One-time handoffs can expire within hours. Review drafts may need a week. Reference material used by a team may need persistent named access instead of endlessly renewed anonymous links. Public documentation needs an archival plan, stable redirects and an owner who can maintain the domain.

Avoid defaulting every link to “never expires.” Defaults become invisible policy. If a long lifetime is justified, write down why and schedule a review. The CISA data security resources emphasise knowing what data an organisation has and protecting it according to risk.

Design the retired state

When a link ends, recipients should see a neutral message—not a recycled destination, an unrelated advertisement or a silent redirect. A good retired page states that the resource is unavailable and gives a safe route back to a current index. It must not reveal the former filename, owner or sensitive context.

Never reuse a random-looking short code for new content. Old messages and crawlers may revisit it. Reuse can accidentally connect two unrelated audiences and makes audit records ambiguous.

Keep a small register

Teams do not need a complex asset-management platform to improve link hygiene. A basic register can include:

  • the public or internal alias;
  • the actual destination or object identifier;
  • the business owner and technical administrator;
  • the data classification and intended audience;
  • creation, expiry and next-review dates;
  • whether downloads and resharing are allowed;
  • the retirement action and incident contact role.

Restrict access to the register because it may reveal sensitive destinations. Preserve enough change history to determine when a redirect moved and who approved it.

Review from the recipient’s side

Test a link while signed out, from a device without cached credentials and after the planned expiry time. Check whether previews, thumbnails or page titles still reveal information. Confirm that search engines were never used as the access-control boundary: a “noindex” instruction is a crawler preference, not authentication.

The most dependable link is not the one that lasts forever. It is the one whose life matches its purpose and whose ending does not surprise the sender or recipient.