Almost no intranet dies on launch day. Launch day is the one day everybody shows up. The death is slower and quieter than that: three months later a policy is out of date, someone gets burned trusting it, word gets around that the intranet "isn't reliable," and within a year you're back where this series started — a ghost town with a beautiful front door. Intranets don't get killed. They die of thirst.

In Part 1 we put up the front door, and in Part 2 we built the rooms behind it. This finale is about the unglamorous discipline that keeps the whole place alive: who's allowed to touch what, how content gets retired before it lies to someone, what the numbers are quietly telling you, and how to get people through the door in the first place. Call it the watering routine.

Permissions: protect the right things, not everything

Governance's first job is access, and Confluence gives you space-level permissions layered on top of global ones — so you decide, space by space, who can view, add, and manage. The instinct when you're nervous is to lock everything down. Resist it. An intranet that's hard to get into is an intranet nobody uses. The better frame is to default to open for the things everyone should see — the handbook, the org chart, the holiday calendar — and reserve tight permissions for the genuinely sensitive: compensation bands, board decks, anything with a lawyer attached. Give each space a named admin who owns its access, and you get local control without a central bottleneck. The goal was never maximum security. It's the right door locked and the rest of the house open.

Content lifecycle: retire it before it lies to someone

Here's the quiet killer, and it isn't wrong content. It's confidently out-of-date content — the page that doesn't announce its own staleness, just sits there looking authoritative until it burns someone who trusted it. A living intranet needs a retirement plan. Confluence lets you archive pages and entire spaces that have outlived their usefulness: out of the way, out of search, but recoverable if you ever need them back. Pair that with ownership — every important page has a name on it and a cadence for review — and lean on automation to flag anything that hasn't been touched in six or twelve months so its owner can confirm, update, or archive it. None of this is glamorous. It's also the whole difference between an intranet people trust and one they've quietly learned to double-check.

Analytics: stop running it on vibes

You don't have to guess at what's working. Confluence's Premium and Enterprise plans include built-in analytics that show you what's actually being read — the popular pages, the quiet corners, how much a space is genuinely used and by whom. That's useful in two directions at once. It tells you what to invest in, because the pages people live in deserve the most care, and it tells you what to prune, because a page nobody has opened in a year is a strong candidate for the archive. It also settles the perennial argument: "nobody uses the intranet" stops being a shrug and becomes a claim you can actually test. Point the numbers at your decisions and maintenance stops being a matter of taste.

Adoption: a front door nobody opens is just a wall

All the governance in the world is wasted if people don't show up, and adoption is a habit you build rather than an email you send. A few moves earn their keep every time. Put the intranet where people already are — linked from Slack, from your Jira and Confluence navigation, from whatever tool they open first — so it isn't a place they have to remember to visit. Seed it with things people genuinely need every week, so the first visit actually pays off. Recruit a handful of champions across teams who keep their own corner fresh and answer "is that on the intranet?" with "yes, right here." And lean on the search we covered last time, so that even people who never learn the structure can simply ask and get an answer. An intranet earns its habit by being reliably faster than asking a human — and it keeps that habit only if the first four sections of this post stay true.

The Avaratak Take

Think of an intranet less like a building you finish and more like a houseplant you keep. It doesn't die from a dramatic event; it dies from a month of nobody watering it. The teams whose intranets are still thriving a year in aren't the ones who launched the prettiest — they're the ones who assigned owners, set a review cadence, watched the analytics, and made the thing genuinely easy to reach. None of that is heavy lifting. It's a standing half-hour on someone's calendar and a culture that treats stale content as a bug rather than a fact of life.

That's also the honest reason we do this as a partner instead of standing up a site and waving goodbye. The build is the easy part. The operating rhythm that keeps a Confluence intranet trustworthy, current, and actually used — the permissions model, the lifecycle habits, the adoption nudges — is where the value quietly compounds, long after the launch confetti is swept up.

And that closes the series: a front door, rooms worth entering, and the watering can that keeps them alive. If you'd like a hand designing any part of it — or a second set of eyes on an intranet that's started to wilt — that's exactly what we do, with your best interests first. Come find us at avaratak.com.