Teamwork Collection

About Teamwork Collection

Teamwork Collection is Atlassian's connected collaboration family for teams that plan work, create and share knowledge, communicate asynchronously, and use AI across that context. Atlassian currently packages Jira, Confluence, Loom and Rovo together in the collection. This page explains the family, its licensing model, buyer fit and how it differs from Atlassian's other collections. Detailed capabilities and prices for each app belong on the individual product pages.

What is included in Atlassian Teamwork Collection?

Atlassian currently lists Jira, Confluence, Loom and Rovo as the core Teamwork Collection apps. Jira handles project planning, tracking and delivery. Confluence provides shared knowledge through documents, whiteboards and related content. Loom adds asynchronous video messages and AI meeting notes. Rovo provides AI search, chat and agents that can use connected work context.

The value of the collection is the relationship between these apps rather than four unrelated subscriptions. Jira work can connect to Confluence knowledge, Loom recordings can be used inside Jira and Confluence cloud experiences, and Rovo can surface context across supported apps. Buyers should still evaluate whether every included app solves a real need, because suite value depends on adoption across the workflows being connected.

How is Teamwork Collection licensed?

Atlassian currently offers Teamwork Collection in Free, Standard, Premium and Enterprise plans. Atlassian's billing documentation says customers purchasing a collection pay one price for the collection rather than separately for each included app. Rovo agents and Atlassian Guard Standard are included with Premium and Enterprise according to the current collection billing documentation.

Exact pricing depends on plan, user count and billing terms, so application-level or current calculated prices should not be copied onto this family page. Procurement teams should compare the collection price with the cost and operational overhead of buying separate apps, while also checking whether users need the same entitlement across the included tools.

How does Teamwork Collection differ from Atlassian's other collections?

Teamwork Collection is aimed at broad collaboration across planning, knowledge and communication. Strategy Collection has a different role: it packages Focus, Talent and Align for strategic planning, workforce alignment and enterprise portfolio execution. Service Collection centers on service delivery through Jira Service Management, Customer Service Management, Assets and Rovo. Software Collection is focused on software delivery with Rovo Dev, DX, Pipelines and Bitbucket, while Product Collection centers on product management workflows.

This separation is important for Brandligo hierarchy. Atlassian is the company. Each collection can serve as a product family where it has a distinct buyer purpose, and the apps inside it are products. An app can appear in Atlassian's broader ecosystem and integrations without turning the company page into a duplicate catalogue.

Who is Teamwork Collection best for?

The collection fits organizations that want project execution, knowledge, asynchronous communication and AI to share context. It is especially relevant when teams already use Jira or Confluence and want to reduce switching between disconnected planning and documentation systems. Cross-functional teams can benefit when project status, decisions, documents and recorded explanations remain linked to the work they describe.

A smaller team that only needs one narrow function may get less value from the collection. A team that mainly needs source control and CI/CD should compare Atlassian's Software Collection. An organization centered on IT service management should compare Service Collection. Large enterprises focused on portfolio governance and strategic allocation should evaluate Strategy Collection instead.

What should buyers check before standardizing on Teamwork Collection?

Buyers should review user counts, plan requirements, identity controls, data residency, AI governance, Marketplace dependencies and migration effort. They should also decide how Jira projects, Confluence spaces, Loom content and Rovo access will be governed so the connected platform does not become harder to administer as adoption grows.

Teams moving from standalone subscriptions should verify current Atlassian billing and migration rules before changing plans. Cloud requirements also matter because some integrations and AI experiences depend on Atlassian Cloud. The collection can simplify purchasing and context sharing, but organizations still need ownership for permissions, content lifecycle, app administration and third-party extensions.