An agency resource hub that survives account managers leaving

The account manager who left took the client with her, sort of

She had the Meta Business Manager link that actually opens the right ad account, the GA4 property that isn't the test one, the client's brand folder three levels down in their Drive, the staging URL, the invoice portal, and the shared password vault entry that everybody references but nobody bookmarked. All of it was in her Chrome bookmarks, in a folder called the client's initials.

Now a new AM inherits the account and spends two weeks reconstructing links from old email threads and Slack scrollback. The client notices. That is not a knowledge management problem in the abstract — it is a billable-hours problem with a name and a date.

The other version of this failure is quieter: three people on the same pod each keep their own slightly different copy of the client's link set, and two of them are wrong about which dashboard is current.

A board per client the agency owns, not the AM

Structure it the way the account is actually run. One board per client. Categories for Ad accounts, Analytics, Assets & brand, Deliverables, Client comms. Subcategories under Assets for logo files, tone-of-voice doc, approved imagery. The board is a workspace asset from the moment it's created, so the person who built it leaving changes nothing about who can reach it.

In an agency the link set is the account handover document — treat it like an asset the company owns, not a folder in someone's browser.

Boards hold more than links, which matters for accounts. Add a text block with the client's approval chain and turnaround expectations. Add a checklist with a recurring cadence for the monthly reporting ritual. Pull the client's shared calendar in as a read-only ICS feed so the pod sees campaign dates without opening a second tool.

• Board per client, owned by the agency workspace
• Groups per pod — share a set of client boards with the whole creative or paid-media pod at once
• "Can share" delegation so a pod lead adds a freelancer without going through an admin
• Per-person view-only for contractors and juniors who should open links, not reorganize them

Pods, freelancers and the day someone rolls off

Share by group, not one person at a time. The paid-media pod gets the eight accounts it runs; the creative pod gets the brand boards. A freelancer brought in for six weeks gets exactly the two boards their scope covers, view-only, and nothing else in the workspace is visible to them.

When they roll off — or when an AM resigns — revoke access in one action. Every link stays. Reassign the board to the successor and the handover is a conversation about the client, not an archaeology dig through someone's bookmarks bar. This is the single operational reason agencies outgrow the shared spreadsheet of links: the spreadsheet is one file with one permission, and nobody ever cleans it.

Client-facing boards, under your brand

On the Business plan a board can be published as a public page at a pretty URL — useful as a client-facing resource hub: everything we made for you, every dashboard you can check yourself, the assets you keep asking for. Five themes (Classic, Gallery, Launcher, Showcase, Card Grid), a header image and tagline, and per-link descriptions and images so it doesn't read like a raw link dump. Protect it with a password-protected share link, or require an account to view.

White-label puts your logo on the app, the extension and the new tab, and on the public pages you send clients. The deliverable stops looking like a third-party tool the client has to learn.

The honest limit: this is a link and resource layer, not a project management system. It doesn't run tasks, timesheets, or approvals, and there are no Slack or Zapier integrations. If your problem is workflow, keep your PM tool — Linksley handles the part your PM tool has never been good at, which is where the actual link lives.