Assets roles and permissions

This page explains how access to Assets works, from assigning product-level roles in AdminHub to managing schema and object type access inside the Assets app.

How access to Assets works

Access to Assets is granted in layers. Each layer builds on the one before it.

AdminHub roles

These roles control access to the Assets app. They are assigned in AdminHub under the Assets app entry.

New schema default behaviour: When a new schema is created, all groups that grant product access to Assets are automatically added to the Object Schema Developers role for that schema.

In-product roles

These roles are assigned inside the Assets app. They control what a user can do within a specific schema or object type. They are separate from AdminHub roles and must be assigned in addition to a product role.

Schema-level roles

Object type-level roles

Object type roles apply to a specific object type within a schema. Use them when you need more granular access control than the schema-level role provides.

Important: Object type roles can override schema-level roles for that specific object type. For example, if a user is an object schema developer but a separate group is assigned as object type developers for a specific object type within that schema, the user's access to that object type is downgraded to object schema user (view only, no create or edit). Their original schema developer permissions apply to all other object types in the schema. To restore their access, add them individually or into the object type developer group for that object type.

Role permissions reference

This table shows what each in-product role can do across the full permission set.

Assets object custom fields on Jira issues

When an Assets object custom field is added to a Jira issue or request type, standard Jira permissions apply. Any Jira user with edit permissions on an issue can add or remove objects in an Assets object custom field, without needing a separate Assets role.

Portal users, including users without any Atlassian license, can view Assets object fields on a request type if the field has been made available on the portal. These roles do not count towards license totals.

What changed with the Assets platform app

Before the Assets platform app launch, Assets access was managed inside JSM settings. It is now managed in AdminHub alongside other Atlassian products.