Every Teams group becomes a department. Members draft, owners publish, admins oversee — and permanent links, QR labels and AI agents all respect the same permissions.
Free · Open source (GPL-3.0) · Built for Microsoft 365
Built on the stack you already have.
Zero user management. Flag a Team as a department and it gets its own space of guides. Membership syncs from Microsoft Graph nightly and refreshes on every login.
No allowlist in the app — Entra assignment is the audience.
Members draft and suggest edits. Owners approve and publish. Admins approve all-staff publishing and deletions. Nobody gets a second password.
Every edit is a revision row; the review queue shows a line diff.
Every guide gets a five-character permanent short link that keeps working when the guide moves or is renamed. Same permission rules, temporary redirect to wherever it lives now.
Short ID assigned at creation, never changes: /a/xxxxx
Print a QR label with the guide's title, department and fallback URL and stick it on the copier, the sound board, the thermostat. Guides also print cleanly and download as DOCX.
Server-rendered SVG label, error-correction Q.
Publish to your department, share with specific groups, or request all-staff publishing. Permissions are resolved from group membership, every time.
A permalink you can't read still tells you which department owns it, so you know whom to ask.
The knowledge base is an MCP server. Connect Claude, Cursor or any remote-MCP client with a work-account sign-in; the agent sees only what that signed-in person can see.
Five tools. Read-only by default. Optional draft creation that never publishes. Admin kill switch.
25 semantic color tokens for light and dark mode, your logo, your sign-in copy — all editable by admins in the browser. Contrast is enforced at 4.5:1 so it stays readable.
Admin → Theme · Admin → Settings · dark mode toggle.
Rich blocks, images, audio and video, Mermaid diagrams. Pasted external images are flagged with a one-click copy so guides don't rot.
Full-text search across everything you're allowed to read. Admins manage tags.
Microsoft Entra ID via SAML. No passwords to reset, no invitations to send.
Every pull request gets a working preview on its own Neon branch. Migrations run on build.
GPL-3.0. No seats, no tiers, no telemetry to a vendor.
Postgres via the Vercel integration.
One enterprise app for sign-in, one registration for sync.
Migrations run on build.
Your groups appear.
Each flagged Team gets a space.
Teams KB deliberately targets one stack so every piece is tested together. Other hosts, databases and identity providers aren't supported yet.
Teams KB is built and maintained by the Tech Ops team at Calvary Albuquerque and given away free under GPL-3.0. If it saves your team time, consider a tax-deductible gift — it keeps the project maintained and the lights on.
Yes. GPL-3.0, no seats, no tiers. Donations are optional and go to Calvary Tech Ops.
A Microsoft 365 tenant with Entra ID, a Vercel account, and Neon Postgres via the Vercel integration.
Not yet. The project deliberately targets one stack so every piece is tested together.
Whoever the group-based visibility says can — same rules in the browser, on permalinks, and for AI agents.
Only if an admin turns on draft creation, and even then they can only create unpublished drafts that go through normal review.
Open an issue or pull request on GitHub; the plans/ folder is where larger changes start.