Confluence

Design Confluence so people can find what they need, trust what they find and keep it up to date.

Overview

Confluence consulting for organisations that have outgrown their wiki

Confluence is Atlassian's workspace for documents and shared knowledge. Teams write pages in spaces, plan on whiteboards, organise structured information in databases, and embed Loom videos and Jira work alongside the text. It connects closely to Jira and Jira Service Management, so requirements, decisions and how-to articles sit next to the work they describe, and Atlassian's AI, Rovo, uses Confluence content to answer questions.

Confluence usually starts well and then sprawls. Spaces multiply, page trees get deep, permissions are granted one person at a time, and nobody knows which of three similar pages is current. That's when people stop searching and start asking colleagues, and it's the point at which most organisations call us. Others come to us replacing an intranet or SharePoint document library, or moving Confluence Data Center to Cloud.

Great Minds is an Atlassian Silver Solution Partner with Atlassian's Cloud Migration Delivery and Service Management Sales accreditations, and we invoice Atlassian licences in Australian dollars. On Confluence projects we design the information architecture and permission model, set up templates and ownership so content stays current, move content from the old tool, and connect Confluence to Jira, Jira Service Management and the rest of your stack.

Capabilities

What we set up in Confluence

Most Confluence work covers the four areas below. We document the decisions in Confluence itself, so the rules for using it are easy to find.

01Space and information architectureA space model that follows how your organisation finds information, with clear home pages, short page trees and labels, so people can browse as well as search.
02Permissions and governanceGroup-based space and page permissions, rules for public links and guest access, page owners and an archiving routine, so sensitive pages stay restricted and stale ones are retired.
03Templates and knowledge for service teamsTemplates for decisions, requirements, meeting notes and runbooks, and knowledge base spaces linked to Jira Service Management so agents and portal users find answers before raising a request.
04Migration and Rovo readinessContent moved from SharePoint, another wiki or Confluence Data Center, cleaned up on the way, and permissions checked so Rovo answers only from content each person is allowed to see.

How we deliver

A Confluence project, from content audit to adoption

We start with what's already there. Most organisations have more good content than they think, buried among duplicates and abandoned pages.

01Audit the content

An inventory of spaces, pages, owners, views and last-edited dates, with the current permission set. We identify what to keep, merge, archive or delete, and which content is sensitive.

02Design the structure

The space model, page hierarchy, templates, labels and permission groups, tested with a few teams on real content before anything moves.

03Build and migrate

Spaces and templates set up, content moved or rewritten in priority order, links and attachments checked, and integrations with Jira and Jira Service Management configured.

04Launch and keep it current

Training for space owners and editors, a short guide to where things live, and an ownership and review routine so the structure still works a year later.

Australian considerations

What Australian organisations should check

Data residency. Confluence Cloud data can be pinned to Australia (Sydney) on Standard, Premium and Enterprise plans, and Confluence has been assessed at IRAP PROTECTED. Set the data residency location before you migrate content, because moving an existing site's data later involves downtime.

Personal information in pages. Confluence often holds staff details, customer information pasted into meeting notes and incident write-ups, and HR process documents. Under the Privacy Act's APP 11, you need to protect that information and remove it when it's no longer needed. We restrict sensitive spaces by group, review public link and anonymous access settings, and set retention for spaces that hold personal information.

Data Center end of life and AUD. Atlassian's Data Center products reach end of life on 28 March 2029, so Confluence Data Center sites need a plan; our Atlassian Cloud migration page covers it. Atlassian invoices Cloud in US dollars, and buying through Great Minds gets you Australian-dollar invoices. See Atlassian licensing in Australia.

FAQ

Confluence questions

Should we use Confluence or SharePoint?

Many organisations use both. SharePoint suits files and documents that live in Microsoft 365, such as contracts and spreadsheets. Confluence suits knowledge that teams write and update together, especially when it relates to work in Jira or Jira Service Management. We help you decide what goes where, so people don't have to guess.

How do we stop Confluence turning into a mess again?

Give every space and key page an owner, use templates for common page types, keep page trees shallow, and archive pages that haven't been touched in a set period. We set up that routine and train space owners to run it.

Can you migrate our content from SharePoint or another wiki?

Yes. We inventory the content first, so only what's worth keeping moves, then migrate it with checks on links, images and attachments. Some formatting has to be rebuilt by hand, and we tell you up front which content that applies to.

Will Rovo show people pages they shouldn't see?

Rovo respects Confluence permissions, so people only get answers from content they can already open. That makes permission clean-up important before rollout: a page shared too widely is a problem with or without AI. Our Atlassian Rovo page covers the rollout.

Can Confluence be used as a knowledge base for Jira Service Management?

Yes. A Confluence space can be linked to a Jira Service Management project, so articles are suggested on the portal and agents can share them on requests. We set up article templates and a review routine so answers stay accurate.

Is Confluence Data Center still an option?

Only for existing customers, and not for long. New customers haven't been able to buy Data Center since 30 March 2026, existing customers can't add users or apps after 30 March 2028, and Data Center reaches end of life on 28 March 2029. New Confluence projects are on Cloud, and Data Center sites should plan the move now.

People

The people who design and run your Confluence work

Our Atlassian team designs Confluence structures, permission models and governance routines from Sydney.

The same consultants who design the space model run the content audit and train your space owners, so the decisions behind the structure aren't lost at hand-over.

Case studies

Confluence and Jira for a global manufacturer

All case studies →

For a premium kitchen appliance manufacturer, we made a dedicated Confluence space the source of truth for product launch strategy, approach and execution, alongside Jira for the launch work. More than 50 teams and 400 tasks now run on one platform.

Let's work together.

Talk to our Atlassian team about the outcome you need.