# Identity Mesh — May 27, 2026

**Release Date**: May 27, 2026\
**Release Type**: Mixed (New Features, Improvements, Bug Fixes)

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

## Overview

This release adds six new connectors — Slack, Salesforce, JumpCloud, OneLogin, HashiCorp Vault, and GitLab — and a tenant-level preference for how timestamps display in the interface. Exports are faster and now match exactly what you see in the filtered asset list. The release also makes missing connector or risk engine components impossible to overlook, and fixes a confusing error message in the onboarding flow.

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

## New features

### Six new connectors: Slack, Salesforce, JumpCloud, OneLogin, HashiCorp Vault, and GitLab

You can now bring identity and secrets data into Mesh from six additional providers:

- **Slack**
- **Salesforce**
- **JumpCloud**
- **OneLogin**
- **HashiCorp Vault**
- **GitLab**

This group focuses on core identity providers and sources of non-human identity secrets, extending risk and correlation coverage across more of your SaaS and infrastructure estate. Further connectors — including Snowflake, Kubernetes, 1Password, Cisco Duo, and BambooHR — are planned for upcoming releases.

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

### Choose how timestamps display for your tenant

Tenant administrators can now choose how interactive timestamps display across the dashboard — in each viewer's browser timezone or in UTC. The setting is on the tenant detail page in the admin area and applies to your whole tenant.

- The choice applies consistently across tables, cards, detail panels, tooltips, modals, and log and report status views.

- Timestamps use a standardized format in both modes — for example "May 27, 2026 3:04:05 PM."

- CSV exports and downloaded files always use UTC, regardless of the display setting, so exported data stays canonical for downstream processing.

- Browser-timezone mode follows daylight saving time rules, and setting changes take effect on subsequent views.

- If the setting is unavailable or invalid, timestamps fall back to the platform-standard display.

This removes ambiguity about how to read timestamps for teams spread across regions.

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

## Improvements

### Faster exports

Export queries have been reworked to reduce latency and load for large exports. Exports complete faster — particularly for tenants with large asset or identity inventories.

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

### Exports match your filtered asset list

Exports now apply the same filters as the asset list view, including Advanced Filters, so the data you export matches exactly what you see and filter on screen. This removes the discrepancy where an export could differ from the on-screen filtered list: what you filter is what you export.

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

## Bug fixes

### Missing connector or risk engine components no longer go unnoticed

Previously, if an internal component of a connector or of the risk engine failed to load, the platform could keep running as though healthy — while the affected connector silently collected no data, or risk evaluation silently ran with some checks missing. The platform now detects this condition immediately at startup and flags it for correction, so it can't surface later as unexplained missing data or under-reported risk. No action is needed.

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

### Onboarding no longer shows a stale error after you enter credentials

During conversational onboarding, an error banner saying the assistant was recovering from a credential-entry problem could stay on screen even after a working credential form had appeared — or after you had already submitted your credentials successfully. A successful step could look failed, prompting unnecessary retries or support requests.

The banner now clears as soon as a working credential form is available or a submission has completed. It remains only when there's genuinely nothing to act on yet.