Aligning Roles for the Future: The Assets Role Alignment Initiative

[#1]

As Atlassian continues to evolve its platform, we’re committed to ensuring a seamless and secure experience for all our customers. One of our latest initiatives is Asset Role Alignment, which aligns user and group roles for the Assets platform as we begin to align with the Platform.

Why Assets Role Alignment?

Historically, access to the Assets platform was managed through Jira Service Management roles. As we move towards making Assets a standalone app within the Admin Hub, it’s essential to ensure that all existing users and groups retain the right level of access—without disruption. Assets Role Alignment is our one-time process to transition permissions from legacy Jira Service Management roles to new, dedicated Assets roles within Atlassian Identity.

What’s Changing?

• Updated Roles for Assets: Assets will now appear as a distinct app in the Admin Hub, with its own set of roles that can be assigned to users and groups.

• Customization of Emails to Users: Now customers will be able to manage how users are notified when they are added to Assets and what role capabilies they have.

• Automated Role Alignment: Existing Jira Service Management Admin and Agent roles will be mapped to corresponding Assets Admin and User roles, respectively, using Atlassian Identity APIs.

What do you need to do?

No action is required on your part. All existing permissions will be transitioned automatically, and your access will remain unchanged.

Looking Ahead

Assets Role Alignment is a foundational step towards a more flexible, secure, and independent Assets platform. By aligning roles now, we’re setting the stage for future enhancements and a better admin experience.

[Dave Mathijs]

@Tori Stitt 

When Assets will be a standalone app in the Admin Hub, will it still be part of the Service Collection and only available to Premium plans?

[Dirk Ronsmans]

@Dave Mathijs ,

It was mentioned at Team 26 Europe that it would still be a part of the Service Collection but that there would also be a "light" version that is available outside of the Service Collection.

Essentially it would be a standalone platform app without Assets Data Manager and with a lower limit of assets. If you also have SC then you also get ADM and a higher assets limit.

/full disclorure: this was mentioned at a booth and details were still to be determined but that was the general idea behind it. This way you could use Assets in other apps but sort of "dumbed down"

@Tori Stitt , anything about this that you can confirm?

Also, regarding the looking ahead, any chance the enhanced flexibility would allow for permissions to Assets being granted based on a AQL?

I'd love to see a possibility where we can set visibility and/or edit rights based on a AQL and not just for an entire object type. (allowing Asset owners to edit only the ones where they are owner and not all the objects within a single object type)

[Tori Stitt]

hey @Dave Mathijs & @Dirk Ronsmans ,

Assets will be it's own App, and have access in the Admin Hub. It will also still be a major pillar in Service Collection. As we stated at Team 25 EU - we are expanding Assets to other editions, products, and collections over this year.

Dirk, your assessment is pretty spot on with it being a light weight standalone App and Data Manager as of now, will not be available to anyone outside of Service Collection Premium and Enterprise. The object limits will be lower as well. 

Stay tuned for more announcements this week and there will be another in February!

[Rune Rasmussen]

Will this change fix the undocumented behaviour where a licensed JSM user with the Object Viewer role would functionally have the Object Schema Users role?

[Joerg]

Automated Role Alignment: Existing Jira Service Management Admin and Agent roles will be mapped to corresponding Assets Admin and User roles, respectively, using Atlassian Identity APIs.

I don't have to worry about JSM Agents getting access to schemas that they previously had no access to, correct?

[Cian Mackle]

When are these changes expected to roll out?

[Fabio Genovese]

@Tori Stitt Does this mean that it will finally be possible to use Assets with any type of project?

How much will the licence cost?

Thanks

FABIO

[Allison Carlson]

Hi @Tori Stitt 

Will a user with the Assets role still use a JSM license, or can they now use a Jira license?

we have some organizations that have users with a JSM Agent license purely so they can update assets , would be good if they could be changed to a Jira license.

Look forward to your response. 
Thank you,

Allison

[Chris Smith]

On what date will this change occur?

[Kai Krause]

Hi,
is there a roadmap , when which feature will arrive ?

BR
Kai 

[Richard Scholtes]

Thanks for the info mail. When does this exactly happen? Because for us - and maybe others - access to JSM and to Assets is not the same people with the same scope of work, so overwriting our current Assets roles with all our JSM Agents and Admins could be security breaking.

[Tori Stitt]

Hi all following up:

Joerg - You do not have to worry about JSM users getting access, no permissions have changed on that front. This shift is to further align teams and permissions across Atlassian. 

Fabio Genovese The goal is to enable the capabilities across the platform yes. You can start using it today and put anything you want in there. We see companies mananging lots of different assets beyond traditional ITAM. For example, inventory, medications, utility vehicles, fish and even office dogs.

Allison Carlson At this time only Jira Service Management or Service Collection Standard/Premium/Enterprise customers will have access to Assets. However, they can now be shared visible depending on your global access in Jira and Confluence.


Chris Smith & Kai Krause It is in a phased roll out with the goal of it finalizing by the 20th. 

Richard Scholtes at this time nothing changes security wise for your team those who have access are still the same folks you have today. This shift is to help give more governance as we move towards getting Assets across the platform. We want to be very mindful that not all assets should be visible to everyone and want to ensure that doesn't happen as we move forward. 

[jan_zubac]

Will these changes affect how permissions in the assets APIs functions or is there nothing to be done there to have it work as before after these changes go live? If I am for example querying asset objects using AQL using the API, and I am using an API-token to call the API, will this work the same way as before when these changes go live?

[Allison Carlson]

 @Tori Stitt to confirm - a user with this role will still need a JSM Agent license .

[Tori Stitt]

Allison Carlson you need a JSM licence if you want them to be able to manage or edit the object on top of viewing it. If you only want them to view it say in a request drop down form, non JSM licenses can do that today. Additionally, it can be surfaced on confluence pages as well to non JSM licenses.