One knowledge base for every room, kept current by your agents
Pages, docs, files, whiteboards and tables in one tree — for a room, a department or the whole company. The AI project manager reads it before it answers, and drafts and suggests edits that a person accepts, so what the company knows stays written down and up to date.
Operations › Release process
Release process
Before you ship
Tag the release, post the change list in the room, and ask QA to check staging. run the staging smoke test and attach its report.
If something breaks
Roll back by hand. Follow the rollback runbook; the on-call engineer owns the call.
Sources · Friday release review · Rollback runbook.pdf
AI Project Manager
Suggests · you review
Upda
The agent writes into the knowledge base, and people approve
Every AI project manager reads the knowledge bases its room can open. When it learns something worth keeping — from a meeting, a thread or a file — it proposes the page or the edit, with its reason and its sources.
- 01
Answers from what is written
The agent searches the room, department and company knowledge bases, including the text inside PDFs and Word files, and cites the pages it used.
- 02
Suggests, never overwrites
Edits arrive inline as suggestions with Accept and Reject, and new pages arrive as drafts. Locked and protected pages are never touched.
- 03
Writes whole pages and docs
Ask for a playbook, a runbook or a policy summary and the agent drafts it as a page or a print-ready doc in the right section of the tree.
Everything a team knows, in one tree
A knowledge base is built from the same rows as room Notes, so nothing is copied and every item keeps one permission model and one trash.
A tree of sections and pages
Sections, pages and sub-pages, dragged into any order, with a Home page pinned at the top of a department or company knowledge base.
Pages that look the part
Icons, covers, callouts, toggles, columns, cards, a table of contents, @mentions and links to other pages, from a “/” menu.
Docs, edited together
Print-layout docs with comments and suggestions, edited by several people at once in real time.
Files, whiteboards and tables
Room files, whiteboards, tables, forms, meetings and Drive or OneDrive links sit in the tree by reference, never copied.
Bring what you already have
Import Word documents as docs, and Notion or Confluence exports as pages with their hierarchy kept.
Share by link
Share a page or doc with anyone, or with your company only. A space owner can share a whole knowledge base; only published items go out.
Three closer looks at a knowledge base
Add any kind of item to the tree, see a page sync into other rooms, and share it by link.
Any kind of item
Pages, docs, tables, whiteboards and files share one tree.
Sync, one copy
Send pages into other rooms you own, read-only or editable.
Sync into rooms you own
1 room see one copy, read-only.
Share by link
With your company, or with anyone who has the link.
qik.mt/shared/note/7f3a…
Opens for signed-in members of your company.
Drafts, personal and protected items never go out.
The same app at every level of the company
In a room it is called Notes. Enabled for a department or the company, the way Announcements are, it is that team’s Knowledge base — with the same tree, editor and agent.
Company and department spaces
The company owner switches on a company knowledge base; each department owner can switch on one for their department.
One sidebar for everything
The Knowledge bases app lists the company, your departments and every room you belong to, with one search across all of them.
Sync without copies
Send chosen pages from one space into other rooms you own, placed under a section you pick, read-only or open for editing.
Roles decide access
Company and workspace owners and admins manage a space; everyone else reads it. Personal notes stay personal.
Knowledge bases · one sidebar
Engineering
- Engineering homeHome
- Release process
- On-call rotation
- Code review guidelines
Same tree, editor and agent at every level. Search runs across every space you can open.
From a conversation to written knowledge
What a team decides in its rooms becomes a page everyone can find, and every agent reads.
A meeting or a thread
Decisions are made in a call, a chat or a file in the room.
The agent drafts
The AI project manager proposes a new page or an edit, citing the meeting and files it came from.
A person accepts
An editor accepts, rejects or publishes the change in the room’s Notes or the team’s knowledge base.
Every agent knows it
The page is searchable across the company and read by agents in every room that can open it.
Who runs on Knowledge base
Runbooks that stay true
After an incident review, the agent suggests the change to the rollback runbook and links the postmortem it came from.
One handbook for everyone
Leave, expense and security policies live in the company knowledge base, and every member’s agent answers from them.
Playbooks from real tickets
Ask for an escalation playbook and the agent drafts one from recent escalations, ready for the team lead to publish.
One company, one office, one shared state
Knowledge base, answered
It is the same app. In a room it is called Notes; switched on for a department or the company it is called Knowledge base. Both have the tree, pages, docs, files and the agent.
No. The agent’s edits arrive as suggestions with Accept and Reject, and its new pages arrive as drafts. Locked and protected pages are never touched, and every change is recorded with who made it.
Yes. Import Notion or Confluence exports as pages with their hierarchy kept, and Word documents as docs.
Members of the company or department read it. Company and workspace owners and admins manage it. A page can also be shared by link with anyone, or with your company only.
Department and company knowledge bases are included in AI Office Pro. Notes in every room are part of every plan, free.
Deploy AI project managers across your office
Unlimited agentic rooms and AI project managers on every plan. Start free, or walk through your office with us.