• Products
  • Get started
  • Documentation
  • Resources

What are roles?

Assets in Jira Service Management is a Premium and Enterprise only feature. Learn more about Assets.

What roles affect

A role is a set of permissions granted to Jira users or groups to view or modify data with Assets. Roles can have three scopes:

  • across all of Assets (Jira admin).

  • for a single object schema (object schema manager, object schema developer, object schema user, or object viewer) and all object types within that schema.

  • for a single object type (object type manager, object type developer, or object type user).

Types of roles

There are five roles in Assets, ranked from least restricted to most restricted :

  1. Jira Admin

  2. Manager (object schema / type)

  3. Developer (object schema / type)

  4. User (object schema / type)

  5. Object viewer (object schema)

Object viewer roles do not require users to have a Jira Service Management license.

The object viewer role grants a user read-only access to all object data contained inside an object schema from outside Assets, including Confluence. Users without a Jira Service Management license do not have access to the schema view within Assets.

Ensure you are comfortable with a user having access to all object data within the schema before you assign the object viewer role.

Users, Groups, and Marketplace apps

Users and Groups can be added as roles within Assets. Any Atlassian Marketplace apps that require Assets permissions will either be added automatically into the Apps column, or can be added manually if required.

How to add users or group roles and permissions for a specific object schema.

How to add users or group roles and permissions for a specific object type.

Object type permissions vs object schema permissions

When do object type permissions override object schema permissions?

It is important to note that permissions for object type roles can override permissions for object schema roles in some cases.

For example, John is an object schema developer for an object schema. A group of users - Frank and Katy - are granted permissions to be object type developers for an object type within this schema. As a result, John loses his permissions to create and edit objects for this object type.

Why? This is because adding the group of Frank and Katy to the object type developer role automatically restricts that role to only those groups or users, overriding John’s permissions as an object schema developer and automatically granting him more restricted permissions for this object type. In this case, John is granted an object schema user role for this object type, which allows him to view objects in this object type but not create or edit them. John retains his original permissions for all other object types within the schema.

There are two possible workarounds for this. The first is to add John into the group with Frank and Katy, and the second is to add him as an individual user for this object type. Either workaround will grant John object type developer permissions for this object schema and allow him to create and edit objects for this object type.

Assets object custom fields permissions

Special permissions apply to users when viewing or editing Assets object custom fields:

  • Any user - even those who are not licensed for Jira Service Management or any Atlassian products - is granted a temporary “User” role when an Assets object custom field is added to a request type which can be accessed by end-users on a portal. This allows them to view the Assets object fields and their values.

  • Jira and JSM users will have temporary "Object Schema User" roles that allow them to view and edit the contents of an Assets object custom field within issues where they already have existing edit permissions.

These roles will not count towards the total number of users on your license.

Role permissions

Permission

Object viewer

Users

Developers

Managers

Jira admins

Create reports on Assets objects via the ‘Reports’ dashboard

 

 

 

 

X

View linked issues panel

 

X

X

X

X

Search for Assets objects and attributes

 

X

X

X

X

View object graph explorer

 

X

X

X

X

View object type graph explorer

 

X

X

X

X

View Assets custom field

 

X

X

X

X

Export objects

 

X

X

X

X

Create Assets object types

 

 

 

X

X

Create/Edit Assets objects

 



X

X

X

Add/Edit/Delete comments

 

 

X

X

X

Delete Assets objects

 





X

X

Create/Edit/Delete Attributes

 





X

X

Modify Assets object schema

 





X

X

Delete Assets object schema

 

 

 



X

Create Assets object schema

 

 





X

Import Assets object schema

 

 

 

X

X

Manage References

 





X

X

Create/Manage Assets custom fields

 

 





X


Move object type (drag & drop)

 





X

X

Delete object type

 

 

 

X

X

Read object data in Confluence Assets macro

X

X

X

X

X

Edit object data in Confluence Assets macro

 

 

 

X

X

 

Still need help?

The Atlassian Community is here for you.