A name everyone agrees on
b/wiki is b/wiki for the whole team. Bookmarks are folder names that drift across teammates and devices.
BookSlash vs Chrome bookmarks
BookSlashvs
Chrome bookmarks
Bookmarks live on one laptop.
Slugs live in the workspace.
Chrome bookmarks are personal recall — folder structure on your laptop, in your browser. BookSlash slugs are shared company memory — every teammate, every browser, every device, with roles and an audit log of who changed what.
The short version
Three reasons teams switch.
- 1
A bookmark belongs to a person and a browser. A slug belongs to a team and a workspace.
- 2
When the URL changes, you update one slug — every teammate keeps the shortcut they already memorised.
- 3
Plus a multi-tool canvas behind every shortcut: invoicing, time tracking, sitemap audits, kanban, mind maps, embeds.
Bookmarks vs shortcuts
A bookmark is personal recall. A slug is shared company memory.
Same idea — quick access to a URL — but the leverage is completely different at team scale. Side-by-side, four times over.
Where it lives
Bookmark folder
On one browser, on one device. Different on every teammate’s laptop.
Shared shortcut
On the workspace, in every browser, on every teammate’s machine.
When the URL changes
Everyone re-bookmarks
Some teammates update theirs. Half the team keeps clicking the dead link.
You update once
The shortcut everyone already knows keeps working — for everyone, immediately.
How a new hire learns it
Asks in Slack
“Where’s the production dashboard?” — a recurring tax on whoever answers.
Memorises ten slugs
b/wiki, b/deploy, b/oncall. Day one productivity, no scavenger hunt.
Who can audit it
Nobody, really
Browser bookmarks have no audit trail. Folders drift. Naming is personal.
Admins, with logs
Roles, custom domains, and a tamper-evident audit log of every edit.
Side by side
BookSlash vs Chrome bookmarks, feature by feature.
| Feature | BookSlash | |
|---|---|---|
Saved URLs | Yes | Yes |
Shared across the whole team | Yes | No |
Memorable named shortcuts (b/wiki, b/deploy) | Yes | No |
Updates propagate automatically Change the URL once; every teammate keeps the shortcut. | Yes | No |
Roles and permissions | Yes | No |
Audit log of edits | Yes | No |
Custom shortcut domain | b.your-co.com on Pro | No |
Multi-tool canvas behind each shortcut | Yes | No |
Invoicing + time tracking | Yes | No |
Cross-browser (Firefox, Edge, Safari, Brave) | Yes | No |
Cost | Free for personal · $5/user/mo (Pro) | Free with Chrome |
Comparison reflects publicly documented features at time of writing. If anything is out of date, email [email protected].
When bookmarks fall over
Six things shared shortcuts give you that bookmarks cannot.
Chrome bookmarks are great for the URL you alone visit weekly. They fall apart the moment "you" becomes "we."
One source of truth, not 47
Update the URL behind a slug once and every teammate is current. Bookmarks live on each laptop and rot quietly.
Roles, permissions, and an audit log
See who created which slug, when it changed, and who has access. Chrome bookmarks have none of this.
A canvas behind the link
Boards with invoicing, time tracking, sitemap audits, kanban, mind maps, embeds. Bookmarks bounce you to a tab.
Search you do not need
You stop searching for the URL because the URL is the shortcut. b/oncall, b/runbook-payments, b/figma — every time.
Real billing tools, not a folder
Invoicing and a Harvest-style time tracker live next to your shortcuts. A bookmark folder cannot send a client an invoice.
We ditched two wikis and a "links" channel. The on-call rotation went from "where's the dashboard?" to "type b/oncall."
RC
Renata Coleman
Eng Lead · Halberd Mobility
Frequently asked
Questions, answered.
No. Most teammates keep their personal bookmarks for personal sites. BookSlash slugs are for the destinations the team needs to share — wikis, dashboards, runbooks, design files, customer accounts. The rule of thumb: if a teammate has ever asked "where is X?", that is a slug.
Yes. Export Chrome bookmarks to HTML, drop the file into BookSlash → Settings → Import, and BookSlash creates a slug per bookmarked URL while preserving the folder structure. You can also bulk-rename slugs after import.
BookSlash ships a free extension for Chrome, Firefox, Edge, Safari, and Brave. The b/* prefix resolves identically in every supported browser, plus Raycast and Spotlight.
Slugs also resolve via a custom domain (b.your-co.com on Pro) and via the workspace web app. Most teams find the extension worth installing for the address-bar trigger, but it is not strictly required.
Drive stars are document-only and personal. BookSlash slugs work for any URL — Google Docs, Figma, Linear, Notion, Slack messages, deploy URLs, dashboards — and they are shared with the whole workspace by default.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial