AssetsAtlassian

Portal Profile for Assets

Give your service desk portal customers a secure, self-service view of the Assets data that belongs to them.

★5

↓17 installs

Overview

Portal Profile for JSM Assets aggregates related data for the portal customer in one place in a simple way. It displays data pulled from one or more JSM Assets object schemas directly on the customer's Portal Profile page, filtered using AQL so each customer only sees what's relevant to them.

Administrators configure one or more named Data Sources, each defined by an AQL query and scoped to a Service Desk and/or Organization. Portal customers can browse the results in either a Matrix or Table view, drill into an object's detailed attributes, and — if the data source is configured as editable — update attributes directly from the portal, with changes written back to Assets.

Features

Key Features

Multi-Schema Data Display

Displays data from multiple JSM Assets object schemas on a single Portal Profile page.

Multi-Schema

AQL-Based Filtering

Uses AQL queries, including currentUser(), to control exactly which objects each portal customer sees.

AQL QueriescurrentUser()

Portal Security Layer

Builds a security layer between the portal customer and the underlying JSM Assets data.

Access Control

Matrix and Table Views

Lets customers switch between a Matrix view and a paginated Table view of their objects.

Matrix ViewTable View

Inline Attribute Editing

Optionally allows portal customers to edit object attributes directly from the profile, syncing changes back to Assets.

Inline Editing

Multiple Configurable Data Sources

Supports several named data sources, each with its own AQL query, scope, and summary attributes, shown as separate tabs.

Multiple Data SourcesTabs

Custom Header and Footer

Supports global or per-data-source header and footer content on the Portal Profile page.

Custom HeaderCustom Footer

Admin Audit and Debug Logging

Gives admins audit logs plus toggleable debug and general logging for troubleshooting.

Audit LogsDebug Logging

Technical Details

Object Schema Users Role (per Object Schema)

Read

The app must be added to the 'Object schema users' role on every JSM Assets Object Schema it queries via AQL (configured on the Roles tab of each Schema); without this the app has no read permission and Data Sources return zero objects.

Service Desk / Organization Scope

Scoped Access

Each Data Source must be scoped to a Service Desk, an Organization, or both, which determines which portal customers see which AQL result set; it is not possible to leave both fields empty.

Editable Data Source (optional)

Read & Write

Admins can mark a Data Source as editable, letting portal customers modify certain object attribute values directly from the Portal Profile page, which writes changes back into JSM Assets (Key, Created Date, and Updated Date always remain read-only).

Admin Tab Access

Admin

Configuring global headers/footers, default result view/count, and viewing Audit or Debug logs is restricted to app administrators.

Known Limitations

A Data Source cannot leave both the Service Desk and Organization scope fields empty at the same time.
The Key, Created Date, and Updated Date attributes cannot be edited from the Portal Profile.

Explore More

Related Assets Products

Cloud Fortified

Microsoft Entra ID (Azure AD) Importer for Assets

Efficiently migrate user, manager, and group data from Microsoft Entra ID (Azure AD) to Atlassian Assets with our secure Forge-powered solution, now available on the Atlassian Marketplace.

★4.8

↓592 installs

Microsoft

Learn More ->