# Identity Mesh — June 17, 2026

**Release Date**: June 17, 2026\
**Release Type**: Mixed (New Features, Improvements)

------------------------------------------------------------------------

## Overview

This release completes filtering for correlated assets on the asset details page, refines the tenant-level timestamp display preference, and corrects a misleading message on the **View in ServiceNow** action.

------------------------------------------------------------------------

## New features

### Filter correlated assets on the asset details page

The previous release ([June 10, 2026](/release-notes/2026-06-10)) added the underlying support for filtering the Correlated Assets section on the asset details page. This release adds the controls: you can now filter the Correlated Assets panel directly, using the same filter dialog and chip interaction you already use on the main NHI asset list.

**What changed:**

- A **Filters** button appears next to the correlated assets header on the asset details page, for all three tabs: Software, Certificate, and Machine.

- The filter dialog offers the same five categories as the asset list: Risk, Platforms, Owners, Organizations, and Locations — no new pattern to learn.

- Filters applied here are scoped to the Correlated Assets panel and kept separate from the main asset list filters, so the two no longer collide or overwrite each other.

- Active filters render as chips below the **Filters** button — including chips for filters that don't affect the currently visible tab, so your full investigation scope stays visible. You can remove chips individually or use **Clear all**.

- Applying, removing, or clearing filters refreshes the active tab, returns you to the first page, updates the header total, and refreshes per-tab counts. Tabs with zero matches show 0 explicitly, and a clear empty state appears when no records match.

- Filters persist as you switch between the Software, Certificate, and Machine tabs, and as you move from asset to asset during the same session.

- If a request fails temporarily, your filter set is preserved so you can retry without rebuilding it.

**Why it matters:** triage of correlation-heavy assets moves from scroll-and-scan to filter-and-inspect, using the same filtering you already know from the asset list.

------------------------------------------------------------------------

### Timestamp display preference refinements

The tenant-level timestamp display preference — **Browser Timezone** or **UTC**, introduced in the [May 27, 2026 release](/release-notes/2026-05-27) — is refined in this release:

- Daylight saving time is now handled correctly when **Browser Timezone** is selected — no inconsistent rendering across transitions.

- Timestamps use one standardized format (for example, Jun 17, 2026 7:47:28 AM) in both modes — only the time zone changes, not the layout.

- Changing the setting takes effect immediately: users pick up the new preference without signing out.

- If the setting is missing or invalid, timestamps fall back to the platform-standard rendering — no broken timestamps.

**Why it matters:** administrators can pick the time zone convention that suits their team without per-user configuration, and the guarantee that exports stay in UTC keeps downstream analysis consistent regardless of the display setting.

------------------------------------------------------------------------

## Improvements

### Clearer message when the ServiceNow integration is not enabled

On the asset details page, the **View in ServiceNow** action is disabled when the ServiceNow integration is not enabled for your tenant. Until now, the message in that state read "ServiceNow ID not available" — wording that suggested the asset lacked a ServiceNow record, when the actual cause was the integration setting.

**What changed:**

- The message now clearly states that the ServiceNow integration is not enabled for the tenant.

- Other disabled states keep their own specific messages.

- If your tenant configuration changes during a session, the message updates on the next page view — no stale wording.

- The behavior of the action when ServiceNow is enabled is unchanged.

**Why it matters:** "the asset doesn't have a ServiceNow ID" and "the integration isn't enabled for your tenant" are different problems — the message now points you at the right one.

------------------------------------------------------------------------