Link Folders and Team Folder Sharing: One Place to Hand Pages to Colleagues

What link folders do

Folders sort the links on your /links dashboard: weekly client reports in one, proposals in another. On Teams and Enterprise, a folder is also how a team that publishes AI-generated HTML hands those pages to colleagues. Share the folder once, and every link filed in it reaches the people you chose, at the access you chose, with no URLs forwarded and no files copied.

One rule shapes the rest: sharing a folder shares the links in it, not the folder. Every link filed there takes the folder's sharing, so filing a link is how you share it, and moving it out ends that.

Organize links into folders (every plan)

Folders work on every plan, Free included, up to 500 per account. A folder belongs to one account and is flat: no subfolders.

1. Create a folder. Press the New folder button (a plus and a folder icon) at the right end of the My links row in the Folders column, and name it.
2. File links. Tick links, choose Move to folder from the bulk bar, pick a destination and press Move; the picker can also create a folder in place. The same bar takes links out of a folder. A link lives in at most one folder.
3. Rename, group or delete. Click the open folder's name to rename it in place. The gear on its row holds Group…, Share… and Delete…. Deleting a folder never deletes a link; its links go back to No folder.

Groups arrange folders under collapsible headings that only you see. They hold folders, not links, and change nothing about who sees what.

Folders live on the dashboard only: the MCP tools and REST API are unchanged, so a page an agent or script publishes arrives in No folder for you to file.

Share a folder with your team (Teams and Enterprise)

Open the folder, press its gear and choose Share…. As the dialog says, everyone you give access to can open every link in the folder. Grant access three ways, in any combination:

• Everyone at your organization, set with one dropdown.
• By role, one row per system or custom role.
• People, added by a member's email address.

Each grant is No access, Can view or Can edit; a named person is removed rather than set to No access. Press Save. A colleague reached by several grants gets the strongest one.

Can view lets a colleague see the links, copy their URLs and read their analytics, views over time and the UTM breakdown, on a shared-link page. Can edit adds changing a link's HTML, title, expiry and password; the change goes live at the existing URL, so a report already sent updates in place, after the same PII, secret and unsafe-URL checks as any edit. An editor sees a note naming whose link it is and which folder shared it.

Whatever the grant, only the folder's owner renames, deletes, groups or re-shares it, or files links in it. Tracking pixels, the custom domain pin, recipient and channel links, and deleting a link stay with the link's owner.

Colleagues find shared folders under Shared with me in the same Folders column, grouped by owner (tiles on narrow screens), with no separate tab.

Worked example: weekly client reports

An analyst builds one report per client each Monday in Claude and publishes them over MCP; four account managers send them, and a second analyst covers corrections.

1. Set up once. The analyst creates a folder, Client weekly reports, and shares it: Everyone at No access, the Account managers role at Can view, the second analyst by email at Can edit.
2. File each Monday. The new reports land in No folder. The analyst ticks them, chooses Move to folder and picks Client weekly reports. That one move shares them.
3. Send and watch. An account manager finds the folder under Shared with me, copies a report's URL into the client email, then checks its analytics page for views.
4. Correct in place. A client flags a wrong figure; the second analyst presses Edit, then Edit HTML, fixes it and saves. The URL in the client's inbox now shows the corrected report.

Limits and governance

• Plans. Folders are on every plan; sharing needs Teams or Enterprise.
• No per-link grants. To share one link, file it in a shared folder; to keep a link to yourself, keep it out of shared folders.
• Grants are read at request time. They count only while the organization is on Teams or Enterprise and the owner is still a member. When someone leaves, their grants and every grant on their folders are removed; a re-invite revives none of them.
• A downgrade pauses sharing. If the organization leaves Teams or Enterprise, grants are kept but unused, and they apply again when it resubscribes.
• Who can share. The folders.share permission is on by default for every system role, including a plain member.

For the analyst, the payoff starts the Monday after setup: the reports publish, one move files them, and every account manager has them at the right access before anyone asks where the link went.