Unifying Assets across the Atlassian Platform

[#1]

If you attended or watched the keynote from Team EU ‘25, we shared that Assets would become its own Platform App and a core part of Atlassian’s Cloud Platform offering—and now you’ll start to see what that really means in your day-to-day work. With this shift, every piece of work gains more context, and every teammate gains speed. Instead of hopping across tools, teams can find, understand, and act on the right asset data in the flow of work.

Asset’s data is starting to become integrated into Teamwork Graph, helping shape the graph and bring in unique data. Making it easier for customer to connect, analize, and report on business objects in Assets across the Atlassian cloud Platform. This enables richer data insights and more powerful automation by linking Assets with other platform data and work.

As a first step, objects from your Assets app are now being woven into the Atlassian Teamwork Graph, so your asset data and work is no longer locked inside a single project or product. The objects and relationships you model will be surfaced across Atlassian apps. That means objects currently in Jira Service Management, can be found with Search and brought into Jira, Confluence pages, app Home, automations, and more. Instead of jumping between tools and systems, assets data comes to you.

These updates are focused on three core areas:

1. Assets everywhere you work (App Home, Rovo Search EAP and Studio)
   Assets is becoming a reusable data layer across Atlassian apps, so key objects in schemas (people, services, devices, vendors) can be linked wherever you’re already working, reducing context‑switching and helping teams make more accurate decisions.

2. A friendlier onboarding experience and new ‘For you'
   Getting started with the Assets app is easy with in-product onboarding and a new “For you” landing page to continue where you left off or see the latest changes.

3. Stronger admin control with in‑context settings and governance
   Admin capabilities have expanded and modernized. In Assets, you can manage admin tools like app usage, global reference types/statuses, icons, themes, banners, and data controls directly within Assets, providing admins clearer governance and simpler oversight from one place.

Together, these updates move Assets to a connected, reusable data layer that powers work across the Atlassian platform and very soon more than Jira Service Management Premium and Enterprise customers will have access as well.

As these changes arrive on your site, we’d love to hear how they help your teams and what you want next in the Assets experience. See more details below. To learn how other companies use Assets, check out our latest webinar with Rover and how they manage more than HAM, but dogs 🐶 too!

---

Unifying Assets across the Platform

When your assets can be found in your daily work flow like App Home, Rovo Search (EAP - natural language/LLM coming soon), and Studio, powered by the Teamwork Graph, every piece of work gains context, and every teammate gains speed. Instead of hopping across tools, teams can find, understand, and act on the right data asset in the flow of work, with relationships (people, projects, work, pages, requests, and more) automatically mapped and kept up-to-date.

The result: less context switching, faster decisions, and smarter collaboration as Atlassian brings all your systems and tools together in one trusted, connected experience.

See Assets app, Schemas, and Objects in App home:

See Schemas and Objects appear in your Rovo Search:

You can now search for objects with Rovo search and see what you just worked on or just updated, in the future we will have a deeper natural language/LLM capabilities.

Get quick access to Studio from Assets:

We’ve added a dedicated Studio app entry point inside Assets so users can quickly switch between Assets and Studio, reducing clicks and context switching.

---

A new Assets in-app product change experience and ‘For you’ navigation

We introduced two ways to help support our customers with onboarding and learning about product updates in the Assets app along with a new ‘For you’ space for everyone to land on when they enter the app.

There is a new in-product changeboarding flow, existing customers will receive a guided tour of the new Assets features. Additionally, new Asset app users will experience an onboarding walkthrough to quickly learn how to use Assets.

Additionally, this will help us to inform and highlight key improvements to our customers to help them understand what’s new and how to get started.

We’ve added a new 'For you' tab to your sidebar navigation, which is now the default landing location for users entering the Assets app. It includes essential product resources, recent places visited by admins and users, and a 'what's next' section. This helps admins find helpful resources and gives agents the ability to hop right back into work.

Both of these updates are aimed to help reduce confusion and training needs by covering the basics and providing more visibility. 

---

A modern, in-context admin experience inside Assets

We’ve modernized the Assets settings page. You can now easily navigate through the various asset settings controls using the left sidebar inside the Assets settings page. We also moved app usage into the settings and added the capabilities to add an Announcement Banner on the Assets screen and the option to change the Asset Theme.

Clearer governance in Admin Hub

We’ve decoupled Assets administration from Jira Service Management and centralized Assets access and configuration in Admin Hub, making it easier for org admins to control who can use Assets. This will help speed up navigation for admins and reduces overwhelm or accidental Asset.

Assets in the Admin Hub, has separate controls for groups and users, org admins can manage Assets roles directly, giving stricter governance over who can view or change data. You can learn more about this here and check out our latest blog on Asset Role Alignment.

---

What Assets admins and users can do next

To make the most of these changes:

1. Review your Assets governance model.

   • Decide which teams should be Assets admins vs. consumers.

   • Use Admin Hub to align groups and roles with that model.

2. Standardize your asset model and visuals.

   • Use Global Reference Types, Statuses, and Icons to align how assets are related, labeled, and displayed.

3. Refresh your onboarding and internal docs.

   • Incorporate the new settings pages, banners, themes, and Studio navigation into how you train new admins and agents.

   • Point existing users to the in-product changeboarding and supplement it with context that’s specific to your org.

4. Check out Rover’s Assets use case webinar - Where Rover’s IT Manager, Kate Brendan, shares how the company uses Atlassian’s Jira Service Management, Assets, and Rovo to streamline access requests, improve cross-team collaboration, cut costs, and even manage office dogs.

Stay tuned for more updates to come!!

[Dave Mathijs]

Yes, I've been waiting for this news, thanks for sharing @Tori Stitt !

[Dang Quang]

Hi Tori, 
It's a good news. I just wonder, currently asset object detailed view is restricted to user with JSM license. I believe this will change too when it appears on the Rovo search, and access is available to more users. 
Also will it mean the Asset object field be available in other Atlassian apps (like Jira software, JPD)? 

[Tori Stitt]

Hi @Dang Quang - there will be restrictions based on user roles and global settings you provide in Assets on who can search and see what objects and schema's. 

In the future, the goal is to have Asset objects appear across the platform of Apps to help keep the right folks in the flow of work instead of jumping between tools and systems, assets data comes to you.

[Michael Bachmann]

As Assets seems to finally get some love after being aquired by Atlassian, will the longstanding issues of Assets now finally be resolved?

The issue search with Assets custom fields has been basically unusable for several years now and the UI of the Assets custom fields within work items is horrendous to say the least (4 clicks minimum to change a single value??).

Since migrating to cloud we have moved away from Assets as much as possible as it has lost most of the features that made Insight so valuable.

I really do hope that Atlassian finally acknowledges the value of Assets and invests into fixing it properly.

[Rodolfo Romero - Adaptavist]

Will this be charged as a separate license? For instance, if someone is paying for JSM now, will they need to pay for Assets separately after this is rolled out?

[Marc-Antoine Marchand]

Great news that this feature is finally coming!

I have a question regarding Assets now being an Atlassian app: does this mean that Asset custom fields will be usable in Jira Software/Work Management projects as well (not only in JSM projects)?

We have some use cases where users need asset information directly inside Jira issues that are not part of a JSM project. Previously, this required a third‑party app using the API to surface asset data in those issues. Based on the information in this post, it sounds like this data might now be accessible to Jira users who have the appropriate Assets permissions.

Can you confirm whether Asset custom fields will be available and usable in non‑JSM Jira projects under this new model?

[Paulo Ramalho]

Adding up to what other users are saying: the fact that we have not been able to display and filter on assets fields in Plans (advanced roadmaps) has been a major blocker for us. Hoping that Atlassian can finally address this with Assets now becoming a platform app. 

[Michael Bachmann]

With Assets having been a Premium only feature up until now and now going free for everyone, what are we left with on Premium in this regard?

[Dirk Ronsmans]

@Michael Bachmann ,

Still to be officially confirmed but the idea is that you get a higher assets limit (and the standard version is more of a taste of what it can do) and also access to Data Manager.

Next to that, Premium Service Collection also has other features of course that you wouldn't have with Standard.

I'm sure a more comprehensive overview will become available soon.

[Rimantas Andrulevičius]

@Tori Stitt Amazing and long waited updates, thank you! 

Maybe I've missed it - but when exactly will this be happening? Does "Very soon" mens end of Q1?

[Venkatesh Reddy Maligireddy]

@Tori Stitt  These are amazing updates. Thank you!

Does this mean, enterprise Jira users (without JSM license) will be able to view Jira Assets and their details (may be in a For You page)? This is currently limited to only a confluence page and the experience is not so great. 

Also, may I know when these changes are rolling out? Thanks!

[Fabian Lim]

@Tori Stitt

Are there any plans to have separate instances within an Enterprise tier organization share the Assets as well? For example, we have the ITSM instance in itsm.atlassian.net with assets schemas and within the same organization, we have the SW instance sw.atlassian.net where software development is being done, but would like to share the same assets as in the itsm.atlassian.net instance.  Ideally, they would be all in the same url instance, but we have clients who like to restrict the sys admins for each instance.

Thanks,

Fabian

[Diane Logsdon]

I must not use Assets to the extent others do. I have read two articles now and I don't understand what is changing or the context(s) that have been shared.

We use Assets currently only to help us with a select few custom fields used in forms that are configured in a couple of our JSM spaces requests. Assets was already moved from the "Work Items" administration area to the left pane where we access our Atlassian products, spaces, etc.

So, what is actually changing? Will this separation cost us more money in our licensing?

Thanks.

Diane

[Nick Daniel]

Hi @Tori Stitt,

On the “What are roles?” page, it states:

“To access Assets, the user must be granted the relevant Assets role and any Jira role.”

Can you clarify whether this means the user must have either a Jira Software license or a Jira Service Management license, or if a specific Jira product license is required?

Thank you!