Every company has a handbook that is a third wrong, because fixing it is harder than ignoring it. Nested pages, real-time editing, per-page permissions and full history, on your own instance, built on the open-source editor European public administrations are building together.
Every company has the same document. It is called something like "Onboarding" or "How we do things", it was written by someone who has since left, it lives in a chat message from two years ago, and roughly a third of it is wrong. Nobody trusts it, so nobody updates it, so it gets more wrong, which is a loop that only ever goes one direction.
The tool is not the whole reason that happens, but the tool decides how much friction stands between noticing something is wrong and fixing it. That is what a wiki is for, and it is why we included one rather than assuming a shared folder of documents would do.
The distinction between a wiki and a folder of documents is structure.
A folder is flat, and finding something means knowing what it was called. A wiki is nested: pages contain pages, so your handbook has a section on expenses, which has a page on travel, which has the specific answer somebody actually needs. The shape carries meaning, and the shape is what makes it browsable by someone who does not yet know the vocabulary. New starters do not know what your documents are called. They know roughly where to look.
Underneath that, search covers everything you have access to, so when the structure fails you, the words still work.
Editing is real-time and collaborative. Two people in the same page see each other's changes as they happen, in a clean block-based editor rather than a page of formatting controls.
The reason this matters for a handbook, specifically, is that the alternative is asynchronous ownership. One person "owns" the document, everyone else emails them corrections, the corrections queue up behind that person's actual job, and the document rots. When anyone who spots a mistake can fix it in the moment, documentation stays close to true.
Which is only safe because of the next two things.
Open editing without a safety net makes people nervous, and nervous people do not edit.
So every page has its own read and write permissions. The salary bands are visible to the people who should see them and invisible to everyone else, in the same wiki, without maintaining a second private one. Granular per page rather than per space, because knowledge does not organise itself neatly into security tiers.
And every page keeps its full history. You can see what changed, when, and who did it, and roll back. That is what converts "anyone can edit" from a risk into a feature: nothing is ever lost, so nobody has to be careful in the way that stops them contributing at all.
Those two together are the entire trick. Permissions mean you can put the real information in. History means you can let people edit it.
Like the drive, your wiki is a complete instance of the software that belongs to you, with its own database and its own storage, at your own address. Not a section of a shared system separated by a permissions flag.
There is one nice consequence of building it that way: your wiki does not exist until somebody asks for it. The first person to open it from the app launcher triggers it being stood up, which takes a moment, and from then on it is simply there. We do not pre-build a wiki for every workspace that may never want one, and you do not have to file a request to get one.
Sign-in is your normal email.eu account, like everything else in the workspace. No separate wiki login, and nobody keeps access after they leave the company.
The editor underneath is La Suite Docs, built as a joint initiative of European public administrations, French and German led, with more joining. That provenance is not decoration. It means the roadmap answers to public bodies with a long-term interest in this software existing, not to an acquisition. Software that runs a government's own documentation does not get shut down because a funding round did not close.
We run it, we keep it current, and we contribute back what we fix. That relationship is the whole reason we could build a workspace at all rather than spending five years writing one.
A reasonable question, since we have both.
Documents are individual things you write, share and send: a proposal, a contract draft, a set of notes. They have a beginning and an end and eventually they are finished.
The wiki is the thing that is never finished. Handbooks, policies, runbooks, the explanation of why an odd decision was made in 2024. Pages that get amended for years by different people.
If it should still be accurate next year, it belongs in the wiki. If it is going to somebody outside the company, it is probably a document.
Wiki is included on every plan, and it is in the app launcher the moment you want it.