Ten years of pages, and permissions to match.
Confluence holds documentation, decisions, and the knowledge a service desk depends on, organized into spaces with their own permission model. Our work is migration, space permission design, and the knowledge structure behind request deflection.
Confluence is where documentation, decisions, and knowledge accumulate, along with the space permissions granted for projects that ended. We migrate it and design the access model rather than carrying the old one across.
What it is
Confluence holds documentation, decisions, and the knowledge a service desk depends on, organized into spaces with their own permission model.
It is for organizations whose knowledge is already there and has been for years, which means the interesting question is not adoption but who can see what.
What it does
Spaces with their own access model
Which is useful, and is also why permissions drift quietly over years.
Knowledge the service desk can use
Articles structured so they surface while a request is being typed rather than after it is filed.
Where it fits
L2, platform and migration, with an L1 problem inside it. Space permissions are where inherited access hides most comfortably, because nobody audits a page. A migration is the one moment that access gets looked at deliberately.
What we do with it
Migration and cleanup
Moving spaces with the permission model redesigned rather than replicated, including the spaces nobody has opened in years.
Space permission design
A group model applied across spaces, covering employees and external vendors on different terms.
Knowledge structure for deflection
Category structure, permissions, and templates so knowledge reduces ticket volume rather than sitting adjacent to it.
Where it earns its place
An organization migrating from Data Center
Space permissions carried across as they were is the default and the mistake. The move is the moment to fix them.
A service desk with knowledge in the wrong place
Procedures held in personal notes or another tool, migrated into a structure the portal can surface.
An estate with external vendors reading spaces
Vendor access to documentation is rarely reviewed and rarely narrow.
Proof
Teamwork Solutions Finalist, 2026
Atlassian Partner Awards, 2026
Questions we get
Do we migrate everything?
What about page-level restrictions?
Licensing
Confluence is licensed per user, and the count usually includes people who read one page a year, which is worth knowing before a renewal rather than after. That reconciliation sits with the rest of the estate in licensing and renewals.