Sharing and access
Every link, file, snippet, and folder is restricted by default. Share it with people by email, open it to anyone with the link, or make it public at its short URL.
Every link, file, snippet, and folder has an access level. New items are restricted: only you and the people you share them with can open them.
Access levels
| Access | Who can open it | Where it opens |
|---|---|---|
| Restricted (default) | You and people you shared it with, signed in | https://linkdash.dev/s/<token> |
Anyone with the link (link) |
Anyone who has the URL | https://linkdash.dev/s/<token> |
Public (public) |
Anyone | The short URL, lida.sh/<slug> or your custom domain |
- The share URL. The token is 24 random lowercase letters and digits, so it can’t be guessed. For a restricted item, everyone else (signed out, or signed in to another account) gets the same not-found page as a URL that doesn’t exist.
- Anyone with the link is not indexed by search engines, but it still unfurls with its social preview in chats.
- Public is how links worked before access levels. Links created before then are public, and nothing changed for them.
- Restricted is the default everywhere: the dashboard, the CLI, the HTTP API, MCP, and CSV import with an empty
accesscolumn. Use public for links you post publicly: social posts, bios, newsletters, printed QR codes. - The slug stays the id. While a link is not public, its short URL returns 404, but the slug stays reserved for it. Make it public again and the same short URL (and any printed QR code) works again.
urlfollows access. Create, get, list, update, copy, and share responses return the share URL unless the link is public, then the short URL. They also includeaccess.
Share with people
Invite any email address, with or without a Linkdash account. Each person you invite gets an invite email with the link.
- People who already have an account get access right away.
- People without one get access once they sign up and verify that email.
- Up to 200 people per item, 50 emails per invite, and 100 invite emails per account per day.
People you share with are viewers unless you make them editors (below). They find the item under Library → Shared and Permissions → Shared with me in the dashboard and open it at its share URL. In the dashboard they see its setup, read-only:
- Every variant with its target, conditions, weight, and status
- The gates: whether there is a password, start, expiry, openings limit, sticky assignment, and forwarded params
- For a folder, the items inside
They never see stats, passwords, your private name, tags, or who else has access. A target behind a password stays hidden until they enter the same password a visitor would. Viewers can’t edit, share, or delete. They see the item by its preview name, folder name, or file name, never your private name.
Editors
Pick Editor when you invite someone, or change a person’s role in the Share dialog. Editors can:
- Change the item’s settings: name, tags, preview, start, expiry, openings limit, sticky assignment, forwarded params, and pausing
- Add, change, and remove variants, and replace files
- See its stats and its Activity: who changed what
- Add links and folders inside a shared folder. They belong to the folder’s owner and count against the owner’s plan.
Editors never add, change, or remove passwords, and they can’t change the slug, domain, or general access, share, delete, move, or copy. Their changes count as events on the owner’s account.
Passwords. A target behind a password stays hidden from editors, the same as from viewers. An editor who enters the same password a visitor would can see and change that variant for 30 minutes. Ten wrong passwords per person per item per hour, then it refuses for the rest of the hour. If the owner changes the password, every unlock ends.
Two people at once. If someone else saved the item while you had its edit form open, saving tells you to reload instead of overwriting their change.
In the dashboard, editors find shared items under Library → Shared and Permissions → Shared with me. From the CLI, API, and MCP they refer to a shared item by its _id or share URL, never by slug.
Folders
- Sharing a folder shares everything inside it, all the way down, including items you add later.
- Opening a folder opens what’s inside. A folder set to anyone with the link, or public, opens everything inside to anyone with the link, even items that are restricted themselves. Those items open at their own share URLs, never at their short URLs unless they are public too.
- Moving an item out of the folder restores its own access.
- The folder page links each item at its short URL if the item is public, else at its share URL.
The dashboard warns you before you open a folder’s access and before you move items into a shared folder.
Permissions
Permissions in the dashboard sidebar lists everything someone other than you can open, in three tabs:
- Shared by me: items you invited people to, with who. Stop sharing removes everyone invited to that item. People who reach it through a shared folder above keep access.
- Open to anyone: items set to anyone with the link or public. An open folder’s row says it opens everything inside, with its item count. Make restricted closes an item, or a folder with everything inside it.
- Shared with me: items other people shared with you. Leave removes one from your dashboard.
Manage opens the same Share dialog as the Library.
Reset the share URL
Reset issues a new token. The old linkdash.dev/s/… URL stops working. People you shared with keep access through the new URL.
A copy
Make a copy keeps the access level but gets its own new share URL. The people you shared the original with are not copied.
From the CLI, API, and MCP
linkdash links create --url https://example.com/launch --access public
linkdash links share q4 --email anna@example.com --email ben@example.com
linkdash links shares q4
linkdash links unshare q4 --email ben@example.com
linkdash links update q4 --access link
linkdash links reset-link q4
linkdash links shared
linkdash links shares
linkdash links leave https://linkdash.dev/s/<token>
linkdash links share q4 --email cara@example.com --role editor
linkdash links unlock https://linkdash.dev/s/<token>
| CLI | HTTP | MCP |
|---|---|---|
links create/update --access restricted|link|public |
access on POST / PATCH /v1/links |
access on links_create / links_update |
links share <id> --email <e> (repeatable, --role viewer|editor) |
POST /v1/links/:id/shares with { "emails": [...], "role"? } |
links_share |
links unshare <id> --email <e> |
DELETE /v1/links/:id/shares/:email |
links_unshare |
links shares <id> |
GET /v1/links/:id/shares |
links_shares |
links shares (no id) |
GET /v1/shares |
links_shares (no id) |
links shared |
GET /v1/shared |
links_shared |
links leave <_id | share URL> |
DELETE /v1/shared/:id |
links_leave |
links role <id> --email <e> --role viewer|editor |
PATCH /v1/links/:id/shares/:email |
links_share_role |
links unlock <_id | share URL> |
POST /v1/links/:id/unlock |
links_unlock |
links activity <id> |
GET /v1/links/:id/activity |
links_activity |
links reset-link <id> (or links update <id> --reset-share-link) |
POST /v1/links/:id/reset-link, or PATCH with resetShareLink: true |
links_update with resetShareLink: true |
All of them take --domain / domain when the slug repeats across your hosts. Share, unshare, an access change, and a reset each count as one event; listing shares and leaving do not. CSV export and import carry an access column. Details: CLI, HTTP API, MCP.

