Solution

Your team's bookmark manager, inside the workspace where the work happens

Drive, repository, design board, metrics dashboard, staging environment. Paste the URL and the shortcut builds itself with title, icon and category, pinned to the sidebar, valid for the whole team.

Start freePricing

No team works in a single tool. It works in twelve, and the path to each one lives somewhere improbable: in one person's bookmarks, in a message pinned three months ago, in a document called "useful links (updated)".

The symptom is always the same and always too small for anyone to fix: the question "what was the link to the dashboard again?" comes back every week, in a different channel, from a different person. Added up over a year, it costs more than any meeting the team tried to cut.

  • Paste the URL, the shortcut builds itself

    Title, icon and category come from the link itself. Creating a shortcut takes less time than sending the message asking for it.

  • Pinned means team-wide

    A pinned shortcut goes to the workspace sidebar and shows up for everyone, it is not one person's bookmark, it is the team's access.

  • Onboarding without forwarding links

    On the first login, whoever joined finds the same set of accesses as the rest of the team. No DM with five URLs.

  • In the same place as the work

    Shortcuts sit next to the tasks, the documents and the email. It is not one more tab to manage the other tabs.

A browser bookmark is not a team access

Browser bookmarks solve one person's problem and create the team's: they live in the profile of whoever saved them, have no owner, no description, and do not survive a change of machine, much less the departure of the person who kept the list.

A shortcut in the workspace is the opposite. It is a shared record: a readable title, a category, an icon, and the URL stored somewhere that already belongs to the team. When someone fixes the link, it stays fixed for everyone at once, not across twelve separate profiles.

The first day of whoever joins

Technical onboarding rarely fails on the big things. It fails on the pile of small ones: figuring out where the right Drive is, which of the three boards is the one that counts, which dashboard leadership looks at on Monday.

When the accesses are pinned in the workspace, that handover stops existing. The person logs in, looks at the sidebar and already has the map of what the team uses, on the same screen as their tasks for the first week. What is left of the onboarding conversation becomes context, not addresses.

Next to the shortcuts, the wiki with the reason for each one. A link without context becomes a chat question in a new hire's first week.

Categories instead of one long list

Every shared list of links dies the same way: it grows until nobody can find anything, and then someone starts a new list. The problem is not the volume, it is the lack of framing.

Each shortcut carries a category, files, design, dev, data, operations, so the hub stays readable past the thirtieth item. What is used daily stays pinned to the sidebar, while the rest remains reachable through workspace search without competing for space.

Shortcuts and integrations solve different things

A shortcut takes you to the tool; an integration brings its content inside. The two coexist, and confusing one for the other is what makes teams use neither properly.

For what needs to stay in sync, there are two-way integrations with Google Drive, GitHub, Google Calendar, Google Sheets and Gmail. For everything else, the internal tool, the client dashboard, the staging environment, the board's spreadsheet, the shortcut is the right answer: a short path, maintained by the team, with no integration project in the way.

An integration is not a shortcut: the Gmail or Outlook inbox opens inside the workspace and a message becomes a task right there, with no copy and paste.

Frequently asked questions

Is this a bookmark manager?
Same idea, but shared and inside the workspace. A browser bookmark lives in one person's profile; a shortcut here is a team record, with title, category and icon, visible to whoever has access to the workspace and kept in a single place.
Who can create and pin shortcuts?
Creating is part of normal work in the workspace, like creating a task or a document. Pinning to the sidebar is the gesture that turns a shortcut into a team access, so that is the point where it makes sense to agree internally on who does it, it applies to the whole workspace.
Do I need an integration for the link to work?
No. The shortcut is just the path: it opens the tool at the URL you pasted, whether that is an internal tool, a client dashboard or a service with no integration at all. The two-way integrations with Drive, GitHub, Calendar, Sheets and Gmail solve a different problem, which is bringing content inside.
Does it work for links that are not tools?
It does. It is common to find the template contract, the brand folder, the time-off form or a vendor's status page in the hub. Any address the team looks for more than once a month is a candidate.
What happens when someone leaves the team?
Nothing is lost, because shortcuts do not belong to a person. They stay in the workspace, the same way tasks and documentation do, which is exactly why the list of accesses should not live in the bookmarks of whoever happened to be maintaining it.
Which plan includes it?
The shortcut hub is part of the workspace, with no separate module. Each plan's limits, people, storage and real-time features, are on the pricing page.

Keep reading

Bring your team's links into one place

Five minutes, no card. Start by pasting the five links your team looks for the most and see how much "what was the link?" disappears.

Start free