Using Openbook as Your Company Intranet

Most intranets fail the same way. A committee picks a portal, IT populates it with policy PDFs, leadership posts a welcome message, and six months later the most recent item on the homepage is that welcome message. The intranet didn't fail because employees hate information. It failed because it was a destination separate from work, and nobody makes a daily trip to a filing cabinet.

The fix is structural: the intranet has to live where work already happens. Openbook is a workspace platform — teams run their boards, docs, and projects in it — which means an intranet built on Openbook sits one click from the work itself. Employees don't visit the intranet; they're already in the building.

Mechanically, Openbook organizes everything as Organization → Space → Room. Your company is the organization. Teams have their own spaces for their own work. The intranet is simply one more space — a company-wide one where every employee is a member — composed from the same 18 room types everything else uses. A social feed, a handbook wiki, an events hub, a Q&A desk, community groups, a time-off room: each is a room you add, not a module you procure.

This guide covers the full build: which rooms to include, how to run the feed and announcements, how the bulletin sidebar and birthdays create daily return visits, how the org chart and directory handle "who do I ask," and a phased rollout plan that avoids the launch-then-tumbleweed pattern.

Design the company space first, then fill it

Resist the urge to create rooms for every conceivable need on day one. An intranet with twelve empty rooms reads as abandoned. Start with a spine of four, add the rest as adoption earns them.

Phase	Room	Type	Job
Launch	Company Feed	Feed	The front page
Launch	Handbook	Wiki	Policies, how-tos, reference
Launch	Events	Event	Everything on the company calendar
Launch	Ask the Company	Q&A	Questions answered once, findably
Week 3–6	Time Off	Time Off	Requests, approvals, who's off
Week 3–6	Pulse	Check-in	Company pulse surveys
As requested	Communities	Group	ERGs, clubs, interest groups
As requested	Company Chat	Chat	Channels and DMs
Later	Company Metrics	Dashboard	Shared numbers

Every space has a customizable sidebar; order it by frequency of use, not org-chart logic. The feed goes first because it's the daily habit. The handbook goes high because "where's the policy" is the second most common intranet errand. Rooms used quarterly can live at the bottom without harm.

Two platform details help here. Openbook supports light and dark mode, so the intranet matches how each person already works. And notifications are delivered both in-app and by email — meaning an announcement can reach an employee who hasn't opened the app that day, which matters most during your first months of building the habit.

The feed is the front page

The Feed room is a Workplace-style social feed, and it's the single most important room in the intranet — it's the reason people come back. What it gives you:

• Posts with images and files. The default unit of company life: a launch screenshot, a photo from the offsite, the new brand deck.
• Announcements as a distinct, visually separate post type, with pinning to keep the ones that matter at the top until they've been seen.
• Polls in five types — everything from a one-tap pulse to a structured multi-option vote. Polls are participation training: someone who has never posted will still tap a poll, and taps become comments become posts.
• Kudos — public recognition as a first-class post type, which gives the feed a steady supply of its best content: people being celebrated by name.
• Events can be posted into the feed, connecting the front page to the calendar.
• Seven emoji reactions and threaded comments with @mentions. Reactions are the low-stakes on-ramp; threads keep conversation attached to its subject; @mentions pull the right person in.

A feed lives or dies on programming. The pattern that works: leadership posts as themselves (short and human beats polished and corporate), the comms owner maintains a weekly rhythm people can predict, every team is invited to post its wins — demo clips, shipped features, closed deals — and comments are open on everything, including hard news. A front page you can't talk back to is just a poster. We've written more about the two-way dynamic in giving employees a voice on the social intranet.

The bulletin sidebar: why people come back daily

Beside the feed stream sits the bulletin board sidebar, and it quietly does the retention work most intranets buy a newsletter tool for. It has four panels:

• Announcements — active announcements, visible even when the stream has moved on. The stream is chronological; the sidebar is persistent. Together they solve the "posted it, but people missed it" problem without spamming.
• Birthdays — today's birthdays, automatically. This sounds trivial and is not: it's a daily-changing, warmly human reason to glance at the intranet, and every birthday generates a small thread of goodwill that costs the company nothing.
• Trending — the posts currently drawing reactions and comments. Trending is your organic "what's going on" digest: a new employee or a returning vacationer catches up in one column.
• Resources — the stable links: handbook sections, the expense tool, the brand folder. This is the "I always forget where that is" panel, and its job is to end the weekly where's-the-link chat message.

Curate the resources panel deliberately — five to ten links that answer the most common errands — and audit it quarterly. Everything else in the sidebar maintains itself.

Announcements that actually land

The announcement is the intranet's core speech act, and most companies do it badly — one post, one channel, one time, then surprise that half the company missed it. Openbook gives you the mechanics to do it properly:

1. Post it as an announcement, not a regular post. The distinct type is a contract with readers: this one matters. Protect that contract by rationing it — routine news goes out as normal posts.
2. Pin it for as long as it's operative. A pinned announcement plus the sidebar's announcements panel means the message survives the stream's churn.
3. Open the comments and staff them. Questions arrive in the thread instead of in thirty DMs, and each answer is answered publicly, once. For genuinely complex changes — a reorg, a benefits overhaul — pair the announcement with a thread in the Ask the Company Q&A room, where answers persist and stay findable (more below).
4. Repeat on a schedule, not on impulse. Big changes get an announcement, a mention in the next leadership post, and a follow-up when the change takes effect. Repetition is a feature; a message heard once was almost heard.
5. For must-see items, lean on notifications. In-app plus email delivery means the announcement reaches people where they are; you don't need a separate email blast tool re-creating the message.

The craft of writing announcements people don't skim past — format, sequencing, worked examples — gets a full treatment in company announcements that do not get ignored.

People: the directory, follows, and the org chart

The most common intranet query isn't a document — it's a person. Who owns billing? Who runs design for the mobile app? Who is my new manager's manager? Openbook answers with platform features, not hand-maintained pages:

• The people directory covers everyone in the organization — searchable, browsable, current because it's the same membership that powers everything else.
• The org chart shows structure: who reports to whom, which is the map every new hire draws by hand in week one at companies that lack one.
• Follow coworkers to see more of specific people's activity — natural for following leadership, cross-team collaborators, or the colleagues whose posts you never want to miss.

Because the directory is a platform layer rather than an HR-maintained page, it doesn't rot the way intranet staff pages famously do. New employee joins the org, directory updates; that's the whole maintenance procedure.

The knowledge layer: handbook, questions, and search

An intranet is judged on whether people can find things. Openbook's knowledge layer has three parts and one shortcut.

The Handbook lives in a Wiki room — a Markdown knowledge base with side-by-side live GitHub-flavored preview. Policies, benefits, how-tos, office guides, security rules: durable reference that anyone can read and designated people maintain. Markdown keeps pages portable and diff-friendly, and the live preview means editors see exactly what readers will.

Working documents live in Docs rooms — a Notion-style block editor with a slash menu, tables, rich blocks, and an infinitely nested page tree with inline search. Teams draft here; the durable results get published to the handbook. The division of labor: Docs is where documents are made, Wiki is where truth is kept.

Ask the Company is a Q&A room — a private Stack Overflow for the questions the handbook hasn't answered yet. Questions in Markdown, organized by tags, with up/downvotes and accepted answers so each question converts into a permanent, findable reference. Its analytics dashboard doubles as a content strategy tool: the questions people actually ask are a ranked list of what the handbook should cover next. The loop — question asked, answer accepted, popular answers promoted into the handbook — is how the knowledge layer grows from real demand rather than committee guesswork.

And over all of it: global ⌘K search. The command palette searches across every room — feed posts, wiki pages, questions, docs, people. One index, one shortcut. The intranet's findability problem is mostly solved by not scattering the content across products in the first place.

The social layer: groups and events

Culture needs rooms of its own, and two types carry it.

Group rooms are member-run communities with their own feed and roster, open or closed, with self-serve join and leave. Use them for ERGs, clubs, guilds, hobby groups, and site-specific communities (the Chicago office, the London office). Open groups suit most communities — discoverability is how they grow; closed groups suit affinity spaces where members control the door. The main feed is the town square; groups are the neighborhood cafés. Both matter, and people who never post in the square often thrive in a café.

The Event room is the shared calendar of company life — all-hands, socials, lunch-and-learns, volunteering days — with upcoming, past, and calendar tabs, RSVP (going/interested), and a discussion thread per event. RSVPs give organizers real headcounts; threads absorb the logistics chatter; the past tab becomes an archive of the company actually being a company, which is worth more to a wavering candidate or a new hire than any culture-deck slide.

The utility layer: time off, chat, and shared numbers

Intranets earn daily visits by being useful, not just informative.

The Time Off room handles PTO end to end — request types, an approval queue (or auto-approve), a "who's off" view, and a team capacity chart. Putting it in the company space means the answer to "is Dana out this week?" is one click from the feed, and every employee interacts with the intranet at least as often as they take vacations — a guaranteed utility loop.

Chat — channels, DMs, presence, typing indicators, unread badges — plus a floating chat widget available on every page, so a quick question doesn't require leaving whatever you're reading. Norm to set: chat for what expires, rooms for what persists. The intranet's value is in the persistent half.

A Dashboard room can serve as the company numbers wall: a drag-and-resize canvas of stat tiles, progress bars, bar and donut charts, and recent-cards tables wired live to boards — plus manual-data and text widgets for figures that live outside any board (revenue milestones, headcount, NPS). Transparency about numbers is a cultural choice; the dashboard makes it a cheap one. Real-time sync means the wall is current without anyone exporting anything.

Governance: who sees what, and who runs it

An intranet needs light governance, and Openbook's roles and permissions keep it simple:

• Roles — Owner, Admin, Member, Viewer — at the space level. Nearly everyone is a Member (post, comment, participate). Admins — comms, HR, IT — manage rooms and structure. Viewer suits contractors or audiences who should read but not post.
• Per-room visibility — each room can be visible to everyone in the space or only to certain people. The company space defaults open; the exceptions (a leadership-only room, a draft-comms room) are deliberate and few. Default to open: an intranet that hides most of itself teaches people it isn't theirs. That principle — and its limits — is the subject of the case for transparent internal communication.
• Multi-tenant organizations mean your company's data is its own tenant, and IT buyers on the Business plan get SSO/SAML, an audit log, API access, and advanced permissions — the checklist items that turn a team tool into company infrastructure.

Assign an owner for each launch room — a name, not a committee. The feed needs a programmer, the handbook needs an editor, Ask the Company needs a responder. Rooms with owners stay alive; rooms owned by "everyone" die.

The intranet as onboarding infrastructure

New hires are the intranet's most motivated users — everything is unknown, and they'd rather look it up than ask. Design their first-week path deliberately:

1. Day one: the directory and the org chart. A new hire's first errand is mapping the humans. The people directory and org chart answer names, faces, and reporting lines without a single awkward question, and following their manager and teammates fills their view with the right activity from hour one.
2. The handbook's "start here" section. Keep a dedicated section of the Wiki for first-week reading — tools, norms, benefits enrollment, how the company communicates. The sidebar's resources panel should link it directly.
3. An introduction post in the feed. The manager (or the new hire) posts a short introduction; reactions and welcome comments do in one thread what a month of hallway introductions used to. It's also the new hire's first evidence that posting here is normal and safe.
4. Groups and events as social on-ramps. Browsing open Group rooms and RSVPing to the next company event gives a remote hire a social path that doesn't depend on office geography.
5. Ask the Company as the pressure valve. Every question a new hire asks in the Q&A room becomes a permanent answer for the next hire. Tell them explicitly: your questions are contributions, not interruptions.

A company that runs this loop finds onboarding docs stay current for free — new hires are the only people who reliably notice what's missing, and the Q&A room captures what they notice.

Measuring whether it's working

You don't need an analytics suite to know if the intranet is alive; the signals are built into the rooms:

• Trending in the feed's bulletin sidebar shows whether anything resonates week to week. A trending panel that never changes is the early warning.
• Poll participation is your cheapest engagement metric. Run a light poll weekly and watch the response count trend, not the absolute number.
• Q&A analytics show question volume and topics. Healthy pattern: volume grows early (people trust the desk), then flattens as accepted answers absorb repeat questions.
• Pulse participation and Team Pulse trends from the Check-in room tell you both how people feel and whether they believe answering changes anything — participation decay is a louder signal than any single result.
• Event RSVPs measure whether company life is reaching people. A "going" count that grows quarter over quarter is culture compounding.

Review these quarterly, in the open, in the feed. Publishing the intranet's own vital signs is the cheapest possible demonstration that the company means the transparency it talks about.

A rollout plan that beats tumbleweed

Intranets die at launch, so stage it:

1. Weeks 1–2, seed privately. Build the space, write ten handbook pages, seed the Q&A with fifteen real questions and accepted answers, queue a week of feed posts. Use per-room visibility to keep it to the build team until it looks inhabited.
2. Week 3, pilot with one friendly department. Watch what they can't find, fix the resources panel and handbook accordingly, recruit three people who'll post in week one.
3. Week 4, launch to everyone. Leadership posts first — personally. Announcement, pinned. One poll in the first week (participation training). The Events room already has the next three company events in it.
4. Weeks 5–8, add utility. Turn on Time Off. Start the pulse cadence in the Check-in room — its Team Pulse analytics and publishable digests give you an engagement read on the intranet itself. Open the first two Group rooms for communities that asked.
5. Quarterly, audit. Trending shows what resonates; Q&A analytics show what's missing; rooms nobody entered get merged or removed. An intranet is a garden, not a monument.

For the philosophical version — what a modern intranet should do and why the old ones failed — see the modern intranet: what it should actually do.

Next steps

The practical path from here:

1. Create the company space and the four launch rooms. Openbook's space templates can jump-start the structure, and the Free plan — $0, unlimited rooms and members, all 18 room types — means the pilot costs nothing.
2. Seed before you invite. An intranet's first impression is its only launch asset.
3. Run the phased rollout above. Four weeks from empty space to company front page is realistic.
4. Grow by demand. Add rooms when someone asks, not when a plan says so.

When you want unlimited history, dashboards, and the AI assistant, Pro is $15/user/month ($12 annual, 14-day Pro trial); Business ($29/user/month, $23 annual) adds SSO/SAML, audit log, and advanced permissions — details at pricing, and the full platform picture at /product.

The intranet your company will actually use is the one sitting next to the work. Build it there.