tl;dr
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
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)
How it impacts you & what you need to know
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.
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
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).
To use an analogy the Space is like a room in a library. Each room can contain different type(s) of information or content.
How it impacts you & what you need to know
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).
To use an analogy content is like the books, magazines, etc. in a library.
How it impacts you & what you need to know
Conclusion
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!
Resources
Robert Hean
Systems Manager & Trainer
Hean
2 accepted answers
1 comment