LogicTrail
  • Trails
  • Check my app
  • Pricing
  • Sign in
  1. Trails
  2. /
  3. Teams and sharing
  4. · 3 minutes · Pro

The share link next door

Your app lets people share a read-only report with a link. A user changed one digit in theirs and opened a stranger's financial report.

This answers: How do I make share links secure? No coding needed. 2 quick decisions.

  • Who may see what
  • Keeping data safe

Checking your access…

How do I make share links secure?

A share link works like a password in a URL, so it must be impossible to guess. Never use sequential numbers or short codes; generate a long random token for each shared item. Let owners revoke links and set expiry, because even unguessable links leak through forwarding, browser history and chat previews.

Trail of the bug
  1. Stranger
  2. Your server
  3. Database

Breaks at Your server: Share links numbered in order

Why AI tools write this bug

AI tools often build share pages on the record's database id, which is usually a counting number, because the page already has it.

How to fix it

  1. Generate a long random token for each share.

3 more steps, and a prompt that checks your own app for this bug. Part of Pro.

Unlock

Common questions

Are UUIDs good enough as share tokens?
Random UUIDs (version 4) are hard to guess. Some UUID versions include time and are more predictable, so prefer a dedicated random token.

Related scenarios

  • The bucket of ID photosPro · 4 min
  • No account with that emailPro · 3 min
  • The avatar that ran codePro · 4 min

More on this trail

Teams and sharing: Removed members who keep access, invites anyone can use, exports that leak other customers, guessable share links.

Want someone to look?

We check AI-built apps for this and three other common leaks, in plain English.

Check my app
Sign in

Sign in to walk this one

2 decisions, about 3 minutes, and a prompt to check your own app for the same problem.

Sign in No password. We email you a link.

How to fix it

  1. Generate a long random token for each share.

3 more steps, and a prompt that checks your own app for this bug. Part of Pro.

Unlock