By 
Teams lose useful pages in chat every week. I kept seeing the same pattern: someone pastes a URL, the thread moves on, and the next person asks again. Shared bookmarks fix that. They only stick when the library has a job, an owner, and a path to share the folder.
This page is the how-to. I create one folder, save links into it, then share that folder with a link. Chat dumps lost. Chat is fast. It also hides the URL after three messages. Five overlapping collections lost too. They make people ask which copy is current.
The path I use
- Create one folder for one job.
- Save new links into that folder, not into a private pile.
- Share the folder with a link when more than one person needs it.
- Pick read-only or read-write. Revoke the link when the job ends.
Create one folder
I start in the workspace that owns the work. Then I open New in the toolbar and choose Folder. The name is the job, not a person: Onboarding references, Product specs in review, Vendor docs for operations. Sibling names stay unique under the same parent. I skipped a dump folder named Team links. That name invites every stray URL.
The click-by-click path is in Create a folder. Folder commands sit on the folder itself. I wrote that up in How to work with folders in the app.
Save links into that folder
A shared folder stays useful only if new saves land there. I use the bookmark manager browser extension on the page I want to keep. A one-line note and a tag for the project or customer make search work later. Save from the folder menu does the same job from inside the hub: the bookmark drops into that folder, not into an unsorted bucket.
Share the folder with a link
I picked a share link over invite-by-email. Invite-by-email is familiar. It also forces every reader through an account. In not24get.me the URL is the credential. Recipients do not need a not24get account to open it. Treat the URL like a secret.
Right-click the folder, or open it and use Share, then choose Share folder. The permission defaults to Read. That is the safest default when people only need to browse. The steps are in Share a folder in read-only mode.
I switch the permission to Read & write when collaborators should add, change, or remove bookmarks inside that folder. They still cannot delete the folder or change sharing. Only the owner can. The steps are in Share a folder with read and write access.
Copy the share link, save if the dialog asks, then send that URL. There is no separate invite-by-email path for folder sharing. Reopen Share and revoke the link when access should stop. After revoke, the old URL fails. A new job gets a new link.
Keep one collection
I keep one shared folder per job, not five copies of the same list. Duplicate folders create doubt. Personal drafts stay in a private folder until they earn a place in the shared one. The rest of how to organize links for your team is one shared folder, not a second chat history.
Permanent teammates who need many folders belong in the organization, not on a single share URL. Folder links are for one collection at a time.