# Getting user attributes from assets asApp

**URL:** <https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763>\
**Category:** Forge\
**Tags:** assets\
**Created:** [September 18, 2026, 1:35pm UTC](https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763 "2026-09-18T13:35:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![KonradGarus1](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/konradgarus1/32/48965_2.png) [@KonradGarus1](https://community.developer.atlassian.com/u/KonradGarus1)\
**Post date:** [September 18, 2026, 1:35pm UTC](https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763/1 "2026-09-18T13:35:13Z")

</div>

I need to read asset objects with user attributes in a background job (think a long-running job triggered via the queue). I’m doing something like:

```auto
api.asApp().requestJira(route`/jsm/assets/workspace/${workspaceId}/v1/object/aql?startAt=0&maxResults=2&includeAttributes=true`, {...})

```

I noticed that all the user attributes are always returned as unknown user, like this:

```auto
{
  "workspaceId": "deadbeef",
  "globalId": "deadbeef:2686",
  "id": "2686",
  "objectTypeAttributeId": "2686",
  "objectAttributeValues": [
    {
      "displayValue": "Unknown user",
      "referencedType": false,
      "user": {
        "avatarUrl": "https://api.atlassian.com/jsm/assets/workspace/deadbeef/v1/avatar/unknown-avatar.png",
        "displayName": "Unknown user",
        "isDeleted": true
      }
    }
  ],
  "objectId": "2884721"
}

```

My app has all the appropriate scopes to see the asset schema. It can run the queries and see all the other attributes.

It also doesn’t have any problems seeing the users in Jira itself. It’s just the assets.

Is this a known restriction on the assets API? Am I missing something? How can I get all this data in a background job in Forge?

---

<div class="post-metadata">

**Author:** ![ibuchanan](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ibuchanan/32/35815_2.png) [@ibuchanan](https://community.developer.atlassian.com/u/ibuchanan)\
**Post date:** [September 18, 2026, 8:45pm UTC](https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763/2 "2026-09-18T20:45:16Z")

</div>

@KonradGarus1,

> [@KonradGarus1](#):
>
> Is this a known restriction on the assets API? Am I missing something?

Yes, known:

- [Forge apps cannot authenticate to the Assets REST API — CMDB scopes return 401 even after forge install --upgrade - #3 by PatrickSifneos](https://community.developer.atlassian.com/t/forge-apps-cannot-authenticate-to-the-assets-rest-api-cmdb-scopes-return-401-even-after-forge-install-upgrade/100939/3)
- [Which assets import tutorial is the most up to date recommendation for using async queues? - #10 by LucasTheisen](https://community.developer.atlassian.com/t/which-assets-import-tutorial-is-the-most-up-to-date-recommendation-for-using-async-queues/100308/11)

But not well documented and not tracked as an issue. It would help to have someone (who is not an Atlassian) log it as [a Suggestion for the Assets platform](https://jira.atlassian.com/projects/ASSETS/issues/). I have channeled the above feedback to the team but they don’t seem to understand the issue on the face of it. My advice is to make sure you explain why it’s a problem, not just state that it is.

> [@KonradGarus1](#):
>
> How can I get all this data in a background job in Forge?

Currently, you have to use `asUser` with impersonation if you are running in a back-end or background context.

---

<div class="post-metadata">

**Author:** ![KonradGarus1](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/konradgarus1/32/48965_2.png) [@KonradGarus1](https://community.developer.atlassian.com/u/KonradGarus1)\
**Post date:** [September 21, 2026, 2:12pm UTC](https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763/3 "2026-09-21T14:12:24Z")

</div>

Thank you, `asUser` with impersonation seems to make the difference. Of course it comes with other drawbacks, but at least it lets us move forward here.

Looks like I can’t see any work items in the ASSETS project you linked. I can’t create them either.

---

<div class="post-metadata">

**Author:** ![ibuchanan](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ibuchanan/32/35815_2.png) [@ibuchanan](https://community.developer.atlassian.com/u/ibuchanan)\
**Post date:** [September 21, 2026, 3:31pm UTC](https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763/4 "2026-09-21T15:31:13Z")

</div>

@KonradGarus1,

Apologies. The ASSETS project is empty on JAC so “can’t see any” is expected. I wan’t expecting, “can’t create”. Can you create suggestions here?[https://jira.atlassian.com/projects/ECO](https://jira.atlassian.com/projects/ECO)

---

<div class="post-metadata">

**Author:** ![KonradGarus1](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/konradgarus1/32/48965_2.png) [@KonradGarus1](https://community.developer.atlassian.com/u/KonradGarus1)\
**Post date:** [September 21, 2026, 4:14pm UTC](https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763/5 "2026-09-21T16:14:23Z")

</div>

I can see the tickets in ECO, but not create one.

---

<div class="post-metadata">

**Author:** ![ibuchanan](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ibuchanan/32/35815_2.png) [@ibuchanan](https://community.developer.atlassian.com/u/ibuchanan)\
**Post date:** [September 22, 2026, 7:56pm UTC](https://community.developer.atlassian.com/t/getting-user-attributes-from-assets-asapp/102763/6 "2026-09-22T19:56:53Z")

</div>

How frustrating. Sorry to send you on a wild goose chase.

See [ECO-1808](https://jira.atlassian.com/browse/ECO-1808). Please watch, vote, and comment.