The links shouldn't leave when the coordinator does

Turnover is the operating condition, not an incident

The volunteer coordinator knew which of the four grant portals was the one with the March deadline, which drive folder had the current board packet, and the exact URL of the donor database login that does not redirect. She left in March. Her successor spent six weeks rediscovering all of it, and will leave in eighteen months.

This is not a failure of documentation. Most small nonprofits do write things down. What does not get written down is the working set of links - the twelve URLs somebody opens every week - because to the person who knows them they are too obvious to be worth recording, right up until they are the only thing missing.

Institutional knowledge is not a document. It is the set of links the last person knew to open.

Volunteers get the board without being told about it

An admin in Linksley can mark a board required. It appears for everyone in the group and cannot be removed, so a new volunteer who installs the browser extension already has the shift board, the sign-in sheet, the safeguarding policy and the who-to-call page - without an orientation email that assumes they read orientation emails.

The extension can also make that board the new-tab page, rendered from a local cache and searchable. For a volunteer using a shared front-desk computer twice a month, that is the difference between a working reference and a bookmark they were shown once.

View-only for volunteers, edit for the people who own it

Grant portals, the donor CRM, the payment processor, the shared drive - these are not links you want reorganized by a well-meaning helper. Linksley caps people at view-only per person, enforced in the web app and in the extension. Program staff get edit rights on the boards they own. A program lead can be given Can share so they add their own volunteers without waiting on the executive director.

Groups keep this from becoming administrative work: a Volunteers group, a Staff group, a Board group, each with the boards that make sense for them and nothing else.

Offboarding that takes one action

When someone rotates off, you revoke their access in a single action and every link stays with the workspace. If they owned a board, it gets reassigned to their successor with its categories intact. Nobody has to email a former volunteer asking which portal the renewal was in.

That is the whole argument for a shared board over a shared spreadsheet of links. A spreadsheet has one permission level and lives in one person's drive; a pinned chat message is four thousand messages up by the time anyone needs it. Neither survives the third handover. If you are also building a first-week page for new staff, new employee onboarding links is the adjacent pattern.

Cost, and where it is not the right tool

The Business plan is nine dollars a month plus two per person with no member cap, so a ten-person organization is around twenty-seven dollars a month. There is a free plan with one board forever and no card, and there are no ads on any plan. Export gives you a standard bookmarks HTML file whenever you want it, so leaving costs nothing either.

Linksley is not a donor CRM, a volunteer scheduler, or a grant tracker, and it has no integrations to connect it to those. It stores links, not records. If your organization is three people who all sign into the same shared Google account, the bookmarks in that account are genuinely enough - the board earns its place once there are volunteers who should see some things and not others.