A front door is a promise. It says something worth entering is on the other side. The fastest way to break that promise is to swing the door open and reveal one enormous room with every document your company has ever produced piled in the middle of the floor.

In Part 1 of this series, we put up the front door: Company Hub, and why an intranet built into Confluence beats the beautiful-but-abandoned kind. Today we walk through it. This is the part where a Confluence intranet becomes rooms people can navigate instead of rubble they give up on — the structure, the content, and the one thing that quietly decides whether any of it gets used.

Spaces are your rooms

Confluence's organizing unit is the space, and the simplest, most durable structure is one space per team or department. Think of each as a room. It has its own customizable homepage — put the team's goals, the links they reach for, and the people who work there front and center — and its own blog for news, wins, and the human stuff that builds culture. Upload your logo and Confluence's look-and-feel shifts to match, a small touch that makes the place feel like yours and quietly helps adoption.

The discipline is resisting two temptations. Don't spin up forty spaces on day one just because your org chart has forty boxes; you'll get sprawl nobody can navigate. And don't cram everything into three mega-spaces either. Mirror how people actually work and where they actually look, then let the structure grow as real need appears. A good intranet has rooms. It doesn't have a hoarder's garage.

Don't move everything — link it

Here's the mistake I watch teams make the moment they decide to "build an intranet": they treat it as a migration project and try to drag every existing document into a new home. Months of copying later, half of it is stale the day it lands. You don't have to work that way. Confluence lets you drop Smart Links straight into the page tree, so a resource that lives somewhere else still shows up where people look for it — without being duplicated. You can embed and edit content from the other tools your teams already use, too: design files, spreadsheets, code repositories. The intranet becomes a hub that points to where things truly live, not a landfill you pour copies into. Less migration, less staleness, more signal.

Make the rooms worth visiting

A room with four blank walls doesn't get used, and neither does a wall-of-text wiki page. This is where Confluence's richer palette earns its keep, because whiteboards, databases, and video all live directly inside a page. A few intranet uses that pull their weight:

• Databases turn a static page into something structured and filterable: a real employee directory, a tools-and-access registry, a policy index, or a "who owns what" table your whole company can search instead of guess at.
• Whiteboards let planning and brainstorms live where the context is — embedded in the page rather than screenshotted into it after the fact.
• Video (and Loom is part of the family now) means a two-minute "welcome from the founder" or a quick how-to sits right on the page, warmer and clearer than a paragraph trying to do the same job.

One newer addition worth knowing: Remix, in open beta as of early 2026, takes a dense section — a data table, a long process description — and turns it into a chart, an infographic, or a timeline. Pages with visuals get read more often, so it's a small feature with an outsized effect on whether anyone actually absorbs what you published.

The part that decides everything: can people find it?

I'll be honest, because that's the job: you can build the tidiest set of rooms in the world and the intranet still fails if people can't find what's inside them. Structure is necessary; it isn't sufficient. What tips a Confluence intranet from "filing cabinet" to "genuinely useful" is that you can ask it. Rovo — now included in every paid Confluence Cloud plan — brings AI-powered search across Confluence, Jira, and connected tools like Slack and Google Drive, and it's permission-aware, so people only ever see what they already have access to. Ask "What's our parental leave policy?" in plain language and you get the answer from your own space, not a list of thirty maybe-relevant pages. Knowledge cards define your company's own acronyms; people cards show who owns what. The gap between an intranet people browse and one they ask is the gap between one they tolerate and one they rely on.

The Avaratak Take

Build in this order: rooms first, then furnishings, then findability. Spaces that mirror how your teams actually work, existing content linked rather than laboriously migrated, pages made worth visiting with databases and video and the occasional Remix, and search sitting at the center of all of it. The trap is doing it backwards — pouring in content before there's a structure to hold it, or standing up spaces faster than anyone can maintain them.

The honest test of a finished intranet isn't how it looks in the launch email. It's whether, six weeks later, finding something is faster than asking a colleague. When that's true, the intranet stops being a place people are told to use and becomes the place they choose to start. That's the outcome we design for — the boring, compounding kind that's still paying off long after the launch confetti is swept up.

In Part 3, the finale: keeping it alive. Permissions that protect the right things without strangling the useful ones, content that gets reviewed and retired instead of quietly rotting, the analytics that tell you what's working, and the handful of moves that get people through the door in the first place.

If you'd rather not draw the floor plan alone, that's our job. As an Atlassian Solution Partner, Avaratak helps teams turn Confluence from a room full of rubble into an intranet with rooms worth entering. Come find us at avaratak.com.