Employee handbook and onboarding wiki software
Onboarding works when a new hire gets one link, not eleven. Flocci Library holds the handbook as a space: policies as nested pages, a first-week checklist they tick as they go, and @mention chips connecting each policy to the team page that applies it — with a public share link for anything readable before day one.
The handbook's job is to answer questions before they are asked, and its failure mode is scatter — leave policy in one tool, the IT setup guide in another, and team norms in someone's head. A single space with a predictable tree fixes that: People → Policies, People → Onboarding, People → Teams.
Make the first week a checklist page rather than a wall of prose. Checklist blocks give a new hire visible progress, and each item can @mention the page that explains it, so the checklist doubles as a map of the handbook.
Some of this can be public before someone signs. A read-only share link on the culture or benefits page is a better recruiting artefact than a PDF, and costs nothing because readers are not seats.
How to set it up
- Create a People space with Policies, Onboarding and Teams as top-level pages.
- Write one policy per page; keep them short enough to read in full.
- Build a first-week checklist page where each item @mentions the page behind it.
- Give each team a page: what they own, who to ask, current priorities.
- Share the culture page publicly for candidates; keep policy pages internal.
Frequently asked questions
Can candidates read parts of the handbook before joining?
Yes — publish the specific pages you want public, such as culture or benefits, as read-only share links. Readers need no account and consume no seat, and you can revoke or rotate the link at any time.
How do I stop the handbook becoming a wall of text nobody reads?
One policy per page, checklists for anything sequential, callouts for the exceptions, and tables for eligibility or leave numbers. Then @mention policies from the team pages that apply them, so people arrive at the right policy from the context they were already in.
Related use cases
Internal wiki software your team will actually use
Internal wiki
Engineering documentation that stays close to the code
Engineering docs
Start writing in Flocci Library
Personal spaces are free — the full editor, backlinks, search, share links and free monthly AI credits. Organisations are ₹49 a seat.
Get started free