Confluence Consulting for Knowledge Bases and Governance
Confluence tends to grow faster than anyone can organise it.
Senzo is an Atlassian Confluence consultant for Australian organisations: we design knowledge bases that Jira Service Management can put in front of customers and agents, and permission models space owners can explain.
When organisations bring us in
- A JSM or Customer Service Management rollout left the knowledge base until last
- The whole space was linked, and customers find pages never meant for them
- An AI agent is planned, and nobody knows which content it should use
- Articles are leaving Zendesk, Freshdesk or ServiceNow and need a structure, not a copy
How a knowledge base reaches your customers
Searches, suggestions and AI answers draw on the knowledge you link. Stale content surfaces stale answers, at scale.
- Suggestions as people typeWith auto-search on, "customers can automatically see recommended articles as they type their requests".
- AI answersOn JSM Premium and Enterprise, the virtual service agent answers from your knowledge base in Slack, Teams and the help center.
- What customers see"Restricted pages won't appear in the help center", and a linked Confluence folder limits which articles reach customers.
- Whether it worksBaseline request volumes first, then use the article reports for views, shares and helpful votes.
A knowledge base readiness check
Before linking a space to a portal or AI agent, we ask six questions.
- AudienceIs customer content separated from agent-only content by space or folder?
- StructureCan someone find an article in two clicks, by what they ask?
- PermissionsIs access granted to groups, and could you explain every grant?
- OwnershipDoes each article show a named owner and its last review date?
- LifecycleCan you retire an article from search without deleting its history?
- FindabilityDo titles use customers' words, tested with real request summaries before go-live?
What a Confluence engagement covers
Scoped in writing after discovery. Your space owners approve the structure and access model before any access changes.
- Knowledge bases for service desksA customer and agent split, linked to your JSM or Customer Service Management space, tested from the portal.
- Permissions and accessToday's access documented, and a group-based model your space owners approve.
- Moving content into ConfluenceThe articles you keep come across from another tool; Data Center moves sit within a Cloud migration.
- AI readinessWhere an AI agent is planned, the readiness question is on our Rovo and Atlassian AI page.
- Ongoing administrationOur managed services cover Confluence administration afterwards.
Frequently asked questions
Can Confluence be the knowledge base for Jira Service Management?
Yes. Atlassian's JSM knowledge base "leverages the power of Confluence" and can link multiple knowledge sources, so first decide which knowledge lives where.
Do our customers need Confluence licences to read articles?
No. Atlassian says anyone with view access to your service desk can read articles "without a Confluence license"; only authors need one. See our licensing page.
What does a Confluence consultant actually change?
Structure and ownership, not content: which spaces exist, who can see and edit what, and who owns each article.
Should customer and agent articles live in separate Confluence spaces?
Often, yes. A separate customer space, or a folder linked on its own, shows what the portal can expose and is easier to audit.
Do we need Confluence Premium for this?
Not for a knowledge base: Atlassian lists an "Embedded knowledge base" on every Service Collection plan, including Free. But permissions and restrictions aren't customisable on Free, so restricting internal content needs a paid plan.
How long does a knowledge base engagement take?
It depends on the spaces, content and groups involved. We size it after discovery, and a first portal-ready set of articles can come early.
Will this get our Confluence ready for Rovo?
Structure, permissions and ownership are the same foundations Rovo relies on. Atlassian's published position is that Rovo honours existing permissions and synchronises with connected apps' access controls, so your permission model becomes the boundary it follows. Use-case readiness is a separate assessment.
Sources (1), last checked 17 October 2026
- Atlassian facts on this page are linked to Atlassian's own documentation where they are used.
What a first conversation should establish
What your Confluence holds, which spaces your service desk would draw on, and what trustworthy articles look like.