Rooms Explained: How to Compose Your Ideal Workspace

Most work tools make one decision for you: here is the app, arrange your team around it. Openbook flips that. You get 18 room types — each a fully-built app — and you arrange the tool around your team.

That freedom is the point, but it also raises the obvious question: which rooms does my team actually need? This guide answers it. We will walk through all 18 room types, what each one is genuinely for, when to reach for it, and when to skip it. Then we will put them together into example compositions for different kinds of teams, because the skill in Openbook is not knowing what a room does — it is knowing which rooms belong together.

First, a thirty-second recap of the structure. Openbook is organized as Organization → Space → Room. Your organization is the company. A space is a workspace for a team, department, project, or community, with its own members, roles, and customizable sidebar. Rooms are the working surfaces inside a space. You compose each space from the rooms that team needs and leave out the rest. If you are brand new, start with Getting Started with Openbook and come back here when you are choosing rooms.

A useful way to hold 18 room types in your head is five families:

Family	Rooms
Communication & community	Feed, Chat, Group, Event
Work management	Table Board, Kanban Board, Gantt, Project Status
Knowledge	Docs, Wiki, Q&A
Visual & review	Whiteboard, Dashboard, Proofing
Rituals & people ops	Check-in, Retrospective, Time Off

Let's take them family by family.

Communication and community rooms

Feed is the Workplace-style social heart of a space. Posts support text, images, files, five types of polls, events, announcements, and kudos. People react with seven emoji reactions and discuss in threaded comments with @mentions. Important posts can be pinned, and a bulletin board sidebar surfaces announcements, birthdays, trending posts, and resources automatically.

Use it when: you want one place for the messages that currently scatter across email, chat blasts, and meetings — announcements, wins, questions to the group, recognition. Almost every space benefits from a feed; it is the room that makes a workspace feel inhabited. Skip it when: the space is a narrow utility (say, a single shared board for two teams) where social context would be noise.

Chat is a Slack-style messenger: channels, direct messages, presence, typing indicators, and unread badges. There is also a floating chat widget available on every page of Openbook, so quick conversations do not require leaving the doc or board you are looking at.

Use it when: your team needs fast, informal, synchronous-ish conversation — and if you are consolidating away from a separate chat tool, this is the room that replaces it. Skip it when: nothing, honestly; but do decide what belongs in chat versus the feed. A rule that works: chat for conversations that expire, feed for messages that should be findable next month.

Group rooms are member-run communities inside your organization: each has open or closed privacy, join and leave controls, its own feed, and its own roster. They are built for the organic social layer — employee resource groups, guilds, book clubs, a running club.

Use it when: people want to organize around identity or interest rather than org chart. Groups are the difference between an intranet people must use and one they want to open. Skip it when: you are setting up a single-team space; groups shine at company scale.

Event rooms are an events hub with upcoming, past, and calendar tabs, RSVP with going and interested states, and a discussion thread per event.

Use it when: your team or company runs recurring events — all-hands, socials, trainings, launch days — and attendance or discussion matters. Skip it when: events are rare enough that a feed post (which can itself carry an event) covers it.

Work management rooms

Table Board is a monday.com-style spreadsheet database. Rows live in colored, draggable groups; columns come in nine types — text, number, status, people, date, tags, checkbox, dropdown, and progress. Bulk actions handle mass edits, and a library of roughly 40 templates covers sales pipelines, content calendars, inventory, and more.

Use it when: your work is structured records: a pipeline of deals, a roster of requests, a catalog of assets, a hiring funnel. If you have ever bent a spreadsheet into a tracker, this is that spreadsheet with the bending built in. Skip it when: work flows through stages and the flow itself matters — that is kanban's job.

Kanban Board is a full agile tool, not just columns of cards. You get board, list, tree, and timeline views; a backlog; sprints with a scrum board and sprint insights; story points; checklists; custom fields; card templates; user-flow diagrams; 36 board templates; and a per-board AI chat.

Use it when: work moves through stages — engineering tickets, content production, design requests — and especially when you run sprints. It scales from a personal to-do column to a multi-squad scrum setup. Skip it when: your data is reference-shaped rather than flow-shaped; use a table board instead. If your team is weighing methodologies, Scrum vs Kanban is the honest comparison.

Gantt is timeline planning: drag to schedule, milestones, drawn dependencies, critical path highlighting, and day, week, or month zoom. It can import from your boards, generate a plan with AI, and ships with 14 templates.

Use it when: dates and dependencies drive the work — launches, events, construction-style projects where task B cannot start until task A ends. Skip it when: your work is continuous flow with no meaningful end date; a Gantt chart of business-as-usual is theater.

Project Status is structured async status reporting: standing questions that get answered on a cadence, a goals board with red-amber-green status, and narrative updates with a history timeline.

Use it when: stakeholders keep asking "how is it going?" and the answer keeps being a meeting. A status room replaces the status meeting with a written record that anyone can read on their own time and scroll back through. Skip it when: the project is small enough that the board tells the whole story.

Knowledge rooms

Docs is a Notion-style block editor: slash menu, tables, rich blocks, an infinitely nested page tree, and inline search. It is the flexible writing surface — meeting notes, proposals, specs, handbooks.

Wiki is a Markdown knowledge base with a side-by-side live preview of GitHub-flavored Markdown. It is the structured writing surface — reference documentation that benefits from plain text's portability and predictability.

These two overlap on purpose, so the real question is which your team should treat as home. Choose Docs when: many contributors, mixed technical comfort, and documents that are as much workspace as reference. Choose Wiki when: the writers think in Markdown (engineers usually do) and the content is reference material with a long shelf life. Plenty of spaces run both — Docs for working documents, Wiki for the canon. We break the decision down fully in Wiki or Docs?.

Q&A is a private Stack Overflow for your organization: Markdown questions with tags, up and down votes, accepted answers, filters, related questions, and an analytics dashboard showing what people ask about.

Use it when: the same questions keep getting answered in chat and then scrolling away forever. Q&A turns answers into assets — searchable, voted, and marked accepted so the next person finds the right one. It is the single best tool for the tribal-knowledge problem. Skip it when: your team is small enough that everyone already knows who knows what — though even then, it is a cheap insurance policy against the day they leave.

Visual and review rooms

Whiteboard is an infinite multiplayer canvas: sticky notes, shapes, connectors, freehand pen, frames, and 11 templates including mind maps, SWOT analyses, customer journeys, and story maps. It is real-time, so a distributed team can think on it together.

Use it when: the work is divergent — brainstorming, mapping, workshopping — and a document would flatten it. Skip it when: the output needs to be structured and durable; whiteboards are where ideas start, boards and docs are where they land.

Dashboard is a drag-and-resize reporting canvas: stat tiles, progress bars, bar and donut charts, recent-cards tables wired live to your boards, plus manual-data and text widgets for numbers that live outside Openbook.

Use it when: someone regularly compiles numbers into a status deck. A dashboard wired to live boards makes that compilation continuous and automatic. Great for exec views, team metrics walls, and client reporting. Skip it when: there is nothing to measure yet — a dashboard of placeholder tiles helps no one.

Proofing is creative review: reviewers pin annotations directly on artwork (time-coded for video), versions are tracked, and each reviewer gives a formal decision — approve or changes required.

Use it when: your team ships visual or video work that other people must sign off on. Proofing replaces the feedback-by-screenshot-and-email cycle with pinned comments and an actual audit trail of who approved what. Agencies and design teams should consider it non-negotiable. Skip it when: nobody reviews creative assets in your workflow.

Ritual and people-ops rooms

Check-in runs async standups and pulse surveys: a 36-template library across industries, scheduled check-ins, mood tracking on a green-yellow-red scale, status flags like Blocked, Help, Milestone, and Kudos, Team Pulse analytics, and publishable digests for people who just want the summary.

Use it when: you have a recurring "how is everyone doing" ritual — daily standup, weekly pulse, project heartbeat — that currently costs a meeting. Skip it when: your team is co-located, tiny, and genuinely happy with its huddle. (Even then, mood tracking over time catches things a huddle misses.)

Retrospective is a real-time retro board with 12 formats — Mad-Sad-Glad, 4Ls, Start-Stop-Continue, and more — and 7 card flavors including GIFs, polls, health checks, and drawings. It supports voting, grouping, an AI-generated meeting summary, CSV export of action items, and a presentation mode for facilitation.

Use it when: your team runs retros, post-mortems, or health checks. Which should be always. Skip it when: you are certain your team never needs to reflect on how it works, in which case we would gently push back.

Time Off is PTO management: request types, an approval queue (or auto-approve if you trust by default), a "who's off" view, and a team capacity chart.

Use it when: time off currently lives in a spreadsheet, an email thread, or someone's memory. The capacity chart alone — seeing at a glance that three of five engineers are out the week of the release — pays for the setup. Skip it when: another HR system already owns PTO and you do not want two sources of truth.

What connects every room

Rooms are apps, but they are not silos. Four platform layers run through all of them:

• The AI assistant works globally and takes real actions — creating tasks, posting updates, inviting members, around 25 tools — with confirmation required for destructive ones. Bring your own key from Anthropic, OpenAI, or DeepSeek.
• ⌘K command search jumps you to any room, doc, or record from anywhere.
• Real-time sync keeps chat, whiteboards, and retros live for everyone at once.
• Roles and permissions apply everywhere: Owner, Admin, Member, and Viewer roles, plus per-room visibility so any room can be open to the space or limited to certain people.

This is why composition works. A card on a board, a page in the wiki, and a post in the feed are all findable from the same search, governed by the same permissions, and reachable by the same assistant.

Pairings: rooms that are better together

Individual rooms solve individual problems. Pairs of rooms solve workflows. These combinations come up so often they are worth learning as patterns.

Whiteboard → Kanban Board. Brainstorm on the canvas — sticky notes, grouping, a story map template — then turn the winners into cards on the board. The whiteboard holds the divergent thinking; the board holds the commitments. Teams that skip the second step end up with beautiful canvases and no shipped work.

Retrospective → Kanban Board. Every retro produces action items, and the Retrospective room exports them to CSV. The teams whose retros actually change anything put those actions on a board with owners and check them at the next retro. Reflection without a tracking surface is venting.

Q&A ↔ Wiki. Q&A captures knowledge at the moment someone needs it; the wiki is where settled knowledge belongs. A monthly pass over your most-viewed and most-voted questions — the Q&A analytics dashboard shows you exactly which ones — tells you what deserves promotion into a proper wiki page. The question thread stays as the trail; the wiki page becomes the canon.

Check-in ↔ Project Status. Check-ins gather ground truth from individuals — what they did, their mood, their blockers. Project Status rolls truth up for stakeholders — goals with RAG status and a narrative update. Run both and the weekly status narrative writes itself from what check-ins already surfaced, instead of from the project lead's memory at 5 p.m. on Friday.

Boards → Gantt. The Gantt room imports from your boards, so execution detail lives on the kanban while the timeline view answers date questions — when milestones land, which dependency chain is critical. Planners get their timeline without asking anyone to maintain two sources of truth.

Boards → Dashboard. Dashboard widgets wire live to boards: stat tiles, progress bars, charts, recent-cards tables. Anywhere a human currently copies numbers into a slide on a schedule, this pair deletes that job.

Feed ← everything. The feed is where other rooms' outputs get an audience: the check-in digest, the sprint's shipped list, the retro summary, the new wiki page worth reading. A short weekly "what happened" post linking into the working rooms keeps the whole space legible to people who do not live in every room.

Example compositions

Here is how the families come together for real teams. Treat these as starting points — every one maps closely to one of Openbook's 12 space templates.

Software team (8 engineers) Kanban Board (sprints, backlog, story points) + Check-in (async standup) + Retrospective (sprint retros) + Q&A (engineering knowledge) + Wiki (technical docs) + Chat. The board is the center of gravity; the check-in room kills the daily meeting; Q&A stops the fourth person from asking how deploys work.

Marketing team (6 people) Feed (campaign announcements, wins) + Table Board (content calendar, from the template library) + Kanban Board (production pipeline) + Docs (briefs and copy) + Dashboard (campaign metrics) + Whiteboard (campaign brainstorms). Structured records and flowing work coexist here, which is why this team wants both board types.

HR / People team Feed (the cultural heartbeat) + Event (company events with RSVPs) + Time Off (PTO and capacity) + Check-in (pulse surveys with mood tracking) + Docs (policies and handbook) + Group rooms (ERGs and clubs). This composition is most of a modern intranet.

Agency client space (one per client) Kanban Board (deliverables) + Proofing (creative review with client approvals) + Dashboard (live client reporting) + Feed (updates the client can see) + Docs (briefs and scopes), with the client invited as Viewers or Members and internal-only rooms hidden via per-room visibility. We wrote a full operating manual for this: Running an Agency on Openbook.

Single project (cross-functional, 12 weeks) Project Status (goals with RAG, weekly narrative) + Gantt (timeline, milestones, critical path) + Kanban Board (execution) + Docs (decisions and specs) + Retrospective (post-mortem at the end). Spin the space up at kickoff, archive it at close.

Company-wide intranet space Feed + Event + Group rooms + Q&A (company-wide questions) + Wiki (the handbook) + the people directory and org chart at the platform level. One space every employee belongs to, surrounded by team spaces.

How to choose, and how to grow

Three rules keep composition honest.

Start with the pain, not the catalog. Do not ask "which of 18 rooms do we want?" Ask "what does my team complain about?" Status meetings nobody likes: Project Status or Check-in. Feedback lost in email: Proofing. The same questions repeatedly: Q&A. Work tracked in a spreadsheet nobody trusts: Table Board or Kanban. Every room earns its place by retiring a complaint.

Launch small, add on demand. Four to six rooms is the right size for a new space. Adding a room takes seconds, so the cost of waiting is near zero, while the cost of sixteen half-empty rooms is a sidebar people stop reading. When someone says "I wish we had a place for X," that is your signal — add the room that week and tell them it was their idea, because it was.

Let different teams compose differently. The engineering space and the marketing space should not look the same. That is not fragmentation — everything still lives in one organization, one search, one directory, one permission model. It is the whole point: one platform, per-team fit, without buying another tool. That consolidation story — one workspace replacing a chat app, a tracker, a docs tool, a whiteboard tool, and a PTO spreadsheet — is what you can see on the product page, and what the free plan (all 18 room types, unlimited rooms and members) lets you test without a procurement conversation. See pricing for where Pro and Business pick up.

Next steps

• Audit your team's current tools and complaints, then sketch a five-room composition on paper before you build it.
• Start from a space template that matches your closest composition, then prune — it is faster than building up from blank. The template-by-template guide: Space Templates: One-Click Workspaces for Every Team.
• If you are setting up your first space today, follow the hour-long walkthrough in Getting Started with Openbook.
• Revisit your composition quarterly. Delete rooms that went quiet, add rooms for new complaints, and keep the sidebar honest.

Seventeen rooms is a lot of catalog. But your team does not need seventeen — it needs the right five or six, arranged in the order people reach for them. Now you know enough to pick them.