---
title: "How to fix JSM Assets access permissions issue in JXL Sheets"
canonical: "https://support.appfire.com/space/SUPPORT/3581444139/How%20to%20fix%20JSM%20Assets%20access%20permissions%20issue%20in%20JXL%20Sheets"
format: markdown
---
This article addresses the issue where Jira Service Management (JSM) Assets objects fail to display in JXL sheets, often showing a "Permission required" error. This happens even for users with Jira Software licenses who are collaborators. The solution involves configuring specific Assets app access and schema-level roles.

### Problem

When displaying an Assets object column in a JXL sheet, users see an error message such as **"Object XXXXX – Permission required"**. 

![image-20260827-124438.png](media://ca8bcd6a-de2c-4d05-ad12-eee892cc8a5d)

### Cause

Atlassian requires explicit authorization in Assets settings for Marketplace apps to read object data on behalf of users. Additionally, users must be recognised as "Assets users" and have appropriate roles within the specific Object Schema.

### Solution

To resolve this, follow these two steps to ensure both the users and the app have the necessary permissions:

#### 1. Grant Assets user access

The users accessing the sheet need to be **Assets users**.

Importantly, this does not mean that the users need to have a Jira Service Management agent license. A user can be an Assets user without holding a JSM agent license.

Your Jira administrator can make the relevant users, or a group containing those users, Assets app users at `admin.atlassian.com`. Atlassian describes the steps here: [<u>Give users access to apps</u>](https://support.atlassian.com/user-management/docs/give-users-access-to-products/)

#### 2. Configure Object schema permissions

Users need permission to view the specific object schemas referenced in the JXL sheet.

1. Navigate to **Assets** → **Object schemas**.
2. Open the specific schema used in your sheet.
3. Go to **Object schema** → **Configure** → **Roles**.
4. Assign the users or their groups to a role.

**Minimum role:** The **User** role is the minimum required to view a schema. The **Object Viewer** role is the most restrictive read-only option.

**Reference:** See Atlassian's documentation on [What are roles?](https://support.atlassian.com/assets/docs/what-are-roles/) for more details.