People & ops
The handbook nobody can't find.
Every company writes the policies down. Almost none of them can tell you whether the version people are reading is the one that's true. Fora's Knowledge Library puts the owner and the date on the shelf, so the answer is visible before anyone acts on it.
Knowledge Library
What's true here, who says so, and when they last checked.
Design 1
Engineering 2
People 2
How we ship
We ship from main. Every change lands behind a flag and is off for everyone.
Flags flip on Tuesday and Thursday at 10:00 Toronto. Nothing flips on a Friday, and nothing flips during launch week without Marcus.
If it isn't written in Fora, it did not happen: the release note is the source of truth, and it links the task it shipped.
Team — we're officially announcing FORA on October 12. All hands behind @Sarah Chen's launch plan.
The library, the doc behind it, and a search that lands on the answer.
One library, and it looks official
A policy page should not look like somebody's draft. The library gives settled answers a different skin from working docs — same tokens, more weight and air — so people can tell the difference without being told.
- Sections by subject — policies, guides, benefits, onboarding
- An Official label with the owner and the last-updated date
- Reader counts, so you can see what's actually being used
- A narrower measure and no editor chrome for people just reading
Knowledge Library
What's true here, who says so, and when they last checked.
Design 1
Engineering 2
People 2
Onboarding that doesn't depend on a buddy remembering
Week one is mostly a person working out who to ask. Fora shortens it by making the company legible: the floor shows who's who, the library holds the answers, and the assistant can point at the thread where a decision was made.
- The handbook, the org chart and the floor on day one
- A new hire can see who everyone is and what they're doing
- Ask Fora AI why something is the way it is, and get the receipts
- Groups for the teams they're joining, with their own feed and files
A reorg that isn't a fortnight of admin
The cost of a reorg is rarely the decision. It's the two weeks afterwards spent renaming channels, re-inviting people and fixing permission lists in six tools. When the org chart is the structure the workspace is built from, that work mostly disappears.
- Departments and reporting lines are first-class structure
- Every team auto-provisions its feed, chat, board and island
- Move a person, and the feed, chat, goals and chart follow
- SCIM keeps it true from your HR system
Questions
Does it sync with our HR system?
Can we keep some spaces genuinely private?
What happens when someone leaves?
Keep reading
Run the whole company from one place.
Start freeFree for up to ten people. No card. Bring the company. Leave the stack.