Oct 28
/
Robert Hean
How Confluence is Structured
There are a ton of features and capabilities in Confluence. They all, however, sit on top of some structure that helps define how they work and what they can do. Here I'll dig into how Confluence is structured and point out how different layers of this structure impact our ability to use this system.
Organization ("Org")

At the very top of every Atlassian product is the Organization (or "Org" for short). Typically, any given company will only have a single Organization - however - this is not true in all cases!
How it impacts you & what you need to know
- At their core Orgs provide a host of access and security controls. For example, this is where you get a license to use a particular product and where groups are maintained.
- For most users most of the time the Org is essentially invisible and they don't even know it exists.
- Groups are maintained here
- An "Org Admin" manages these
Site ("Instance")

Beneath the Org is one or more sites. Each site can have up to one copy of any Atlassian product (e.g. Confluence) and the site is typically where any given user interacts with the system. It is possible for one Org to have multiple sites - you can tell which site you're on by looking at the URL when you log into Cloud (e.g. "some name" is the site name in [some name].atlassian.net). In the screenshot above the site is "one-atlas-tecz".
How it impacts you & what you need to know
- Each site is its own copy of Confluence with its own settings, permissions etc
- A "site admin" can maintain this layer
- Most users most of the time will only interact with a single Confluence site and won't even realize this exists.
- A site can contain multiple Atlassian products (e.g. Jira and Confluence) - this allows for easy integration/linking
- Most company's using Atlassian products may have a single site - but they could have more (e.g. one for European and one for Asian workers).
Application ("App")

This is your version of Confluence - what you log into and maintain your content in. An App always lives in one, and only one, site - although your organization may have several sites, each of which may have a different copy of Confluence within it. The screenshot above shows the "For You" page of the Confluence app.
To use an analogy the "App" would be like a physical library building. This building houses everything within the library.
How it impacts you & what you need to know
- This is what people log into
- "App Admins" maintain settings for the app
- Lives in one, and only one, site
- Most company's using Confluence will have a single App - but they could have multiple apps (but each one is in its own site).
- Contains all the information/pages/content/settings for that copy of Confluence
Space

This is a container with the App and houses between 0 and many pieces of content (pages,blogs,databases, etc, more on this below). The screenshot above shows a number of difference spaces, include some for projects and others for teams.
To use an analogy the Space is like a room in a library. Each room can contain different type(s) of information or content.
See more here
How it impacts you & what you need to know
- "Space admins" maintain spaces (including permissions)
- Most people most of the time will work in a small number of spaces
- Spaces can be organized by department, project, or anything else
- Spaces can be archived and/or deleted
Content

This is the actual stuff found within Confluence - the pages, blogs, whiteboards, smart links and databases that your team uses. The exact type of content available is controlled at the space level, and content can be restricted (only specific groups or people can view and/or edit it). The screenshot above shows a space with content in it (the list on the left) and the types of content that be added in the drop down.
To use an analogy content is like the books, magazines, etc. in a library.
See more here
How it impacts you & what you need to know
- Most people most of the time interact with this level
- This is what most people think of when they think of Confluence
- There is no effective limit to how much content you can create
- Content can include attachments, links, videos, images and almost anything else
- The ability to create, edit, archive and delete content is controlled at the space level
Wrap Up
It does feel like there's a lot of layers - but keep in mind most of the time you'll mainly be working with Content or Spaces. The other 3 (Org, Site, App) are just something to know about in case it comes up.
Hope you found this useful (if so hit the like button!) and please comment with your questions. Some more links below, and have a great day!
Looking for more?
Write your awesome label here.
Join our newsletter!
Thank you!
