TL;DR
IT teams often answer the same tickets (VPN, passwords, printers) because Confluence documentation is hard to find, inconsistent and impossible to measure.
Meridian Knowledge Structure for Confluence solves this with four apps:
– SubSpace Navigation for a clear site-wide menu
– Metadata for Confluence for consistent tagging and filtering
– Navitabs Steps for step-by-step procedures
– Viewtracker Content Reports to see which articles are read and which need rewriting
Employees solve common issues themselves, and IT uses usage data to continuously improve documentation.
It’s Monday, 8:47 a.m., and Rita already knows what’s waiting in her queue.
Three password resets. Two printer problems. And a VPN ticket, because there’s always a VPN ticket.
Rita is an IT Support Specialist, and she’s good at her job. That’s part of the problem. She answers the same questions so often she could do it in her sleep, and every time she does, a ticket that actually needs a specialist waits a little longer.
The frustrating part? The answers already exist. They’re somewhere in Confluence: in a page from 2021, in a draft someone never finished, in a long article that explains VPN setup for three laptop models at once. Employees can’t find them, and when they do, they don’t trust them to be current. So they do the sensible thing and open a ticket.
If this sounds familiar, you’re not alone. Most IT teams don’t have a documentation problem. They have a findability, structure and feedback problem.
How employees solve IT issues themselves in Confluence
John got a new laptop on Friday. On Monday morning, he can’t connect to the VPN.
Old John would have opened a ticket and waited. New John opens the IT Service Documentation space in Confluence.
1. Organize IT documentation with a site-wide navigation menu
At the top of Confluence, a site-wide menu built with SubSpace Navigation shows four clear categories:
- Accounts & Access
- Hardware
- Network & VPN
- Software Requests
John doesn’t search or guess. He clicks Network & VPN.
2. Tag and filter IT articles with metadata
Every IT article is tagged with Metadata for Confluence fields: service area, device type, urgency and last-reviewed date. Because the fields are built into the IT article template, every page is tagged the same way.
John filters by his device type. Instead of scrolling through twelve VPN articles, he sees the one written for his laptop. The last-reviewed date also tells him it’s current, so he trusts it.
3. Break how-to guides into clear steps
The article doesn’t arrive as one long page. With the Steps design in Navitabs – Navigation Macros for Confluence, the VPN setup is broken into a clear sequence. John completes step one, moves to step two, and never has to scan a page to find where he left off.
Four minutes later, he’s connected. No ticket, no waiting, and no Rita.
Meanwhile, Rita gets something she never had: evidence.
How to measure whether your IT documentation works
Self-service is only half the story. The other half is knowing whether the documentation works.
Before, Rita could only guess. A spike in VPN tickets might mean the article was missing, wrong, or just hard to find. Ticket volume alone couldn’t tell her which.
Now, every Monday, she opens Viewtracker’s Content Reports for the IT documentation space. And one week, the data shows her something odd.
- The VPN Setup article is the second most-viewed page in the space, with 1,240 views in the past 30 days.
- In the same period, IT still received 86 VPN-related tickets.
High traffic plus unresolved tickets is a clear signal. People are finding the article. It just isn’t solving their problem.
Use page analytics to find articles that need a rewrite
So Rita rewrites it. She splits it by device type, restructures it with Navitabs Steps, and updates the last-reviewed date. Over the next month, Viewtracker shows views holding steady while VPN tickets drop to 19.
For the first time, Rita can show her manager that the documentation is working, with data, not anecdotes.
Pro tip: Combine the last-reviewed date metadata field with Metadata for Confluence’s reporting to list articles that are both overdue for review and heavily viewed in Viewtracker. That’s your rewrite priority list, built automatically.
How Meridian Knowledge Structure for Confluence supports IT self-service
Each of the four apps in Meridian Knowledge Structure for Confluence solves one part of the problem:
| Problem | App | What it does |
|---|---|---|
| “I don’t know where to look.” | SubSpace Navigation | Site-wide menu with clear top-level categories |
| “There are too many articles, and I don’t know which one is current.” | Metadata for Confluence | Consistent tags for filtering and reporting |
| “This page is too long to follow while I’m working.” | Navitabs | Steps design for procedural content |
| “We don’t know which docs work.” | Viewtracker | Content Reports and update signals for each article |
Each one helps on its own. Together, they form a loop: employees find answers → they solve the issue themselves → usage data shows what to improve → the documentation gets better → more issues get solved without a ticket.
Benefits of self-service IT documentation
- Employees like John fix common issues in minutes instead of waiting in a queue.
- IT specialists like Rita spend less time on repetitive first-line tickets and more time on work that needs their expertise.
- IT leads can show documentation is effective (or find where it isn’t) with real engagement data.
- The organization gets fewer tickets, shorter wait times and a better employee experience with IT.
And because Viewtracker data keeps guiding updates, the documentation improves every week.
How to start building an IT self-service knowledge base in Confluence
You don’t need to restructure all of your IT documentation at once. Pick the one ticket type that keeps coming back, whether it’s VPN, passwords or printers. Give it a clear home, consistent tags and step-by-step instructions, then watch what Viewtracker tells you.
That’s where Rita started, and her Monday queue looks very different now.
Explore Meridian Knowledge Structure for Confluence or book a demo with our team.
Frequently asked questions
Couldn’t find what you need?
Build a self-service IT documentation space that employees can easily navigate, filter and follow. Combine clear navigation (SubSpace Navigation), consistent page tagging (Metadata for Confluence), step-by-step procedures (Navitabs Steps) and usage analytics (Viewtracker) so you can find and fix articles that aren’t working.
It’s Elevatic’s bundle of four Confluence Cloud apps: SubSpace Navigation for Confluence, Metadata for Confluence, Navitabs – Navigation Macros for Confluence and Viewtracker – Analytics for Confluence. Together, they help teams structure, tag, present and measure knowledge in Confluence.
Use Viewtracker’s Content Reports to see views per article. Compare them with ticket volume for the same topic. If an article gets a lot of views but tickets keep coming in, people are finding it, but it isn’t solving their problem, so you need to rewrite it.
Start with a few clear top-level categories, such as Accounts & Access, Hardware, Network & VPN and Software Requests. Expose them in a site-wide menu and use an article template with metadata fields like service area, device type, urgency and last-reviewed date so every page is tagged the same way.
Use the Navitabs Steps design to split procedures like VPN setup, device enrolment or printer configuration into a clear sequence. Users can then work through the steps one at a time while they fix the issue.