The Atlassian Teamwork Collection and the Service Collection change how most organizations buy Atlassian Cloud. Instead of licensing Jira, Confluence, Loom, and Jira Service Management one app at a time, you now buy bundles built around how teams work. This guide explains what each collection includes, how licensing works, and what IT leaders should decide before their next renewal.
What the Atlassian Teamwork Collection includes
Atlassian introduced the Teamwork Collection on April 9, 2025, at Team ’25. It brings together Jira, Confluence, Loom, and Rovo agents for teamwork. According to Atlassian’s licensing page, it also includes access to Atlassian platform apps. In addition, Premium and Enterprise customers receive Atlassian Guard Standard at no additional cost.
The idea is simple. Jira holds the plan and the work, and Confluence holds the knowledge. Meanwhile, Loom carries the conversation between them, and Rovo connects all three through the Teamwork Graph. As a result, an AI agent can read a requirements page, look at related work items, and draft an update with real context.
Atlassian has kept adding to the bundle. At Team ’25 Europe in October 2025, it announced the ability to assign Jira work items to agents, starting with Rovo Dev for code tasks. It also added Rovo skills that break large work into smaller tasks, plus Loom bug reports recorded from inside Jira.
What the Service Collection includes
The Service Collection does the same thing for service teams. Atlassian launched it at Team ’25 Europe in October 2025. Atlassian sells its four apps only as a bundle:
- Jira Service Management for internal IT and business service desks.
- Customer Service Management, a newer app for external customer support.
- Assets for tracking services, configuration items, and dependencies.
- Rovo AI experiences and agents for request triage, incident response, and knowledge creation.
For existing Jira Service Management customers, Atlassian states that moving to the Service Collection keeps current access and configurations. It also adds Customer Service Management. Therefore, the move is mostly a packaging change for teams already on the platform.
How Atlassian Teamwork Collection licensing compares
Both collections are Cloud only. However, they count users differently. Atlassian licenses the Teamwork Collection per user and the Service Collection per agent. The table below summarizes the published allowances for the Service Collection.
| Allowance | Standard | Premium | Enterprise |
|---|---|---|---|
| Assets objects included | 5,000 | 50,000 | 500,000 |
| Automation steps | 3,000 | 6,500 | 9,500 |
| Rovo credits | 250 | 700 | 1,500 |
| Virtual Service Agent assisted conversations | Not included | 1,000 per month | 1,000 per month |
A few licensing details matter for planning. First, the Teamwork Collection Free plan covers up to 10 users, and the Service Collection Free plan covers up to 3 agents. Second, Teamwork Collection Enterprise requires an annual contract for 801 or more users and allows up to 150 instances of each app. Third, apps inside a collection cannot be swapped for other products. Finally, Atlassian notes that customers with an active subscription may receive a credit for unused time when they move into a collection.
Five decisions to make before your renewal
Collections can lower total cost and simplify administration. Still, the value depends on your current footprint. We recommend working through these five questions with your Atlassian admin and procurement team.
- Who actually uses Confluence and Loom? If most Jira users also live in Confluence, the Atlassian Teamwork Collection usually makes sense. If only a small group does, compare the bundle against separate licenses.
- Do you already pay for Atlassian Guard? Guard Standard is included with Teamwork Collection Premium and Enterprise. Consequently, a separate Guard subscription may become redundant.
- How large is your CMDB? Count your configuration items before choosing an edition. Atlassian bills Assets objects above the included limit as usage.
- Who will govern Rovo? Rovo credits are included, but agents still need an owner, usage rules, and permission reviews.
- Are you still on Data Center? Collections are Cloud only. As a result, they belong in your migration plan rather than your Data Center renewal.
What this means for regulated organizations
Banks, health plans, and public agencies should treat a move to the Atlassian Teamwork Collection or Service Collection as a platform change. For example, Rovo agents read across Jira and Confluence, so page and project permissions become AI permissions. Similarly, Customer Service Management may bring external customers into the same Cloud site as internal teams.
Before you switch, review four controls. Confirm identity and SSO through Atlassian Guard. Next, check data residency and the compliance attestations your regulators expect on Atlassian’s Trust Center. Then clean up open Confluence spaces that an agent could summarize. Finally, document who approves new agents and automation rules.
If you are planning a move from another ITSM tool, our 90-day ServiceNow to Jira Service Management plan covers the cutover steps. For the portfolio side of the platform, see our guide to the Atlassian Strategy Collection.
Frequently asked questions
Can I still buy Jira or Confluence on its own?
Yes. When Atlassian announced the Atlassian Teamwork Collection, it confirmed that customers can still buy Jira, Confluence, Loom, and Rovo individually. The Service Collection is different, because its apps are sold only together.
Do existing Jira Service Management customers lose any configuration?
No. Atlassian states that moving to the Service Collection keeps your current Jira Service Management access and configurations. It also adds Customer Service Management to the subscription.
Is Atlassian Guard included in the Teamwork Collection?
Atlassian Guard Standard is included at no additional cost for Teamwork Collection Premium and Enterprise customers. Our Atlassian Guard and Entra ID setup guide explains how to configure it.
How VTPMO can help
VTPMO is a team of Atlassian platform specialists with Atlassian Certified Professionals on staff. We help organizations compare collection options, plan the move to Cloud, and set up Rovo with clear governance. Explore our Atlassian services, Jira Service Management services, and cloud migration services, or talk with us before your next renewal.
Sources
- Atlassian: Introducing Atlassian’s Teamwork Collection (April 9, 2025)
- Atlassian: Teamwork Collection licensing
- Atlassian: Teamwork Collection updates from Team ’25 Europe
- Atlassian: Service Collection overview
- Atlassian: Service Collection licensing
- Eficode: Atlassian launches the Service Collection (October 2025)