Admin Configuration

The Admin tab has three tabs: Connection Settings, Application Settings and Advanced Features.

You can view the current status of an import here and cancel it if needed.

This section displays the import history, including details such as:

• Status

• Triggered By

• Result

• Type

• Start Time

• End Time

• Duration

You can also review detailed statistics of objects and export them to an Excel file for further analysis or chart creation.

These settings control the timing and batch size of Graph API requests made during background imports. The Graph API may return throttling errors if requests are made too frequently. By adjusting the page limit and batch delay, you can reduce the rate of requests at the cost of slower imports.

• Page Limit: Number of records fetched per API request. If you increase this by 100, also increase the batch delay by 10 seconds.

• Batch Delay: Time to wait between batches of API requests.

Note: These are advanced settings. Only change them if you are experiencing throttling errors during large imports.

Under the Admin tab, you can select the Object Types you wish to import. Update these settings and enable or disable any Object Types that are not relevant to your organisation's use cases.

The Attributes section lets you choose which User properties to import. Disable any attributes that are unnecessary for your implementation.

We've recently added an option to import group owners. Select this option if you want group owners to be included in the import.

Note: Some group filters may not work when group owner import is enabled.

By default, all groups are imported regardless of whether they have members. You can enable the option to skip groups that have no members during import. This is useful for keeping your Assets schema clean when many empty groups exist in your Entra ID tenant.

This filter refines which users are written to Assets. It operates on User object attributes.

Example: displayName startsWith 'John'

Refer to the Filter documentation for all supported filter expressions.

This filter refines which groups are written to Assets. It operates on Group object attributes.

Example: displayName contains 'Team'

This filter refines which devices are written to Assets. It operates on Device object attributes.

Example: operatingSystem eq 'Windows'

When enabled, only users who are members of the groups matched by the Groups Filter will be imported. Group and user filters will work in conjunction — useful if you want to import only users from specific departments or teams.

Note: This option only applies to full imports, not test imports. When enabled, even if no user filter is set, only users assigned to the filtered groups will be imported.

We've recently added an option to import directory extensions. Directory extensions provide developers with a strongly typed, discoverable and filterable extension experience for directory objects.

The Microsoft Entra ID Importer allows you to map directory extension attributes from your Azure AD applications to predefined fields in the User object schema.

• 20 Pre-defined Extension Attribute Slots: The User object schema includes 20 dedicated directory extension attribute fields (directoryExtensionAttribute1 through directoryExtensionAttribute20)

• Application Selection: The system retrieves all Azure AD applications in your tenant using the Microsoft Graph API endpoint: applications?$select=id,displayName,appId

• Extension Property Discovery: For each selected application, the system fetches available extension properties using: applications/{appId}/extensionProperties

• Attribute Mapping: You can map any extension property from your applications to one of the 20 available slots. These mappings are stored securely and included in user data imports.

• Dynamic Import: During user imports, the mapped extension attributes are automatically included in the Microsoft Graph API query alongside standard user attributes.

1. Navigate to Admin → Connection Settings → Directory Extension Attributes (Beta)

2. Click Edit Extension Attributes to reveal the configuration form

3. For each attribute slot (1–20):

   • Click Select to open the attribute picker modal

   • Choose an application from the dropdown

   • Select the specific extension attribute from that application

   • The attribute name will populate automatically

4. Click Save Attributes to store your mappings

• Storage: Extension attribute mappings are stored in the DirectoryCustomAttributes secret storage

• API Integration: Extension attributes are appended to the user query using the $select parameter

• Schema Mapping: Each attribute slot maps to a corresponding field in the JSM Assets User object

• Empty Values: Only non-empty attribute values are included in the final import

Minimum version: 4.19.0 or later is required. We strongly recommend upgrading to the latest version.

Displays the current health status of your JSM Assets object schema. Click Check Schema Status to verify that your schema is correctly configured and up to date with the latest object types and attributes.

As of version 6.33.0, individual schema items can be restored independently. Each object type and attribute listed in the Schema Status panel has its own Restore button, allowing you to fix only the items that need attention without triggering a full schema reset.

Configure automatic error notifications for scheduled imports. When a scheduled (hourly or daily) import encounters errors, the app can notify you via a Jira Cloud Automation webhook.

1. In Jira, go to Project settings → Automation and create a new rule with a Web Trigger as the entry point.

2. Configure the rule to send a notification (e.g. email, Slack, or a comment) when triggered.

3. Copy the webhook URL from the Web Trigger configuration.

4. Return to Admin → Application Settings → Set Up Automation Notifications and paste the webhook URL into the field.

5. Click Set Automation Notification to save.

After setup, any failed scheduled import will trigger your automation rule and send a notification.

Audit logs provide a detailed record of all changes made within the application — including configuration changes and import operations. Click Show Audit Logs to view the history.

If you experience unexpected behaviour or misconfigured imports, the audit log is the first place to check.

Debug logs capture detailed diagnostic information about the application's internal operations.

• Show Debug Logs: View the current debug log output.

• Enable Debug Logs: Activates verbose logging. Enable this before reproducing a problem, then share the output with Pio support for troubleshooting.

Note: Disable debug logs after troubleshooting is complete to avoid unnecessary storage usage.

Deletes all data stored by the application except Audit Logs. This includes import configurations, extension attribute mappings, and cached data.

Important: This action does not remove the JSM Assets object schemas you have created. To fully clean up, you must also delete the object schema separately in JSM Assets.

Use this option only when you need to completely reconfigure the application from scratch.

This tab holds the features of the Advanced edition: identity checks, alerts, Jira tickets and licence savings. Your edition is shown next to the title, for example "You're on the Advanced edition".

• On Advanced: set up and run the checks here.

• On Standard: the tab shows what Advanced offers and how to upgrade. Settings can't be changed.

• After moving back to Standard: your earlier Advanced settings and alerts stay visible, read-only.

Shows the last run and the last successful run of the checks, with Run now and the schedule: after each successful import (default), every hour or once a day.

One card per check: Credential expiry, Disabled users with licenses, Inactive users and guests and MFA posture. Each card has:

An estimate of the licence spend you could recover from disabled and inactive users. Click Licence prices to set what you pay per licence. Licences without a price count at the default price of $20 a month until you set your own.

For everything about the Advanced edition, see Advanced Edition: Identity Monitoring and Licence Savings.