Candidate
A proposed link with a reason and intended collection.
Team bookmarks
Create a shared link library people can trust—not another dumping ground.
Use collection charters, candidate and approved states, clear owners, access rules, canonical links, and risk-based review dates.
Collection charterOwner & backupApproved linksReview cadence
Collection charter
Give every shared board a service, audience, and owner
A one-paragraph charter prevents vague collections from absorbing every link the team encounters.
Record these decisions
- Purpose and primary audience
- What belongs and what does not
- Owner and backup owner
- Who may propose, approve, edit, and archive
- Tag vocabulary and naming convention
- Review cadence and archive policy
Example charter
Support runbooks contains the canonical troubleshooting and escalation links used by support leads. Anyone on Support may propose a link; the Operations owner approves or archives. High-risk links are reviewed monthly. Credentials and case-specific tickets do not belong.
Make the charter visible at the point of contribution, not hidden in a separate policy document.
Lifecycle
Separate suggestion from trust
Users should be able to see whether a link is a lead, reviewed resource, canonical destination, or historical record.
Reviewed
Relevance, access, source, title, and duplication have been checked.
Canonical
The preferred link for a recurring task, answer, policy, or tool.
Archive
Retained for history but removed from active views and onboarding paths.
Safety and access
A URL can reveal more than the destination
Titles, collection names, query strings, and shared context can expose confidential projects even when the page requires login.
Match permissions
Place links only in spaces whose access matches the underlying work. Create a curated external collection for partners.
Keep secrets elsewhere
Never store passwords, tokens, or temporary access keys in bookmark titles, notes, or URLs.
Prefer stable destinations
Use maintained landing pages when possible; label dated files, filtered views, and mirrors clearly.
Useful first collections
Start where repeated searching already costs time
A small trusted collection proves the workflow before organization-wide migration.
New-hire setup
Required links grouped by first-day and first-project outcomes.
Customer proof
Approved case studies, public examples, and reusable evidence.
Support canonicals
Runbooks, policies, status pages, and escalation destinations.
Competitor evidence
Dated observations connected to canonical pricing, docs, and product pages.