Skip to main content
Sign in

May 2026

  • June 05, 2026 16:13
  • Updated

May ’26 Release: Architecting the Future

Asset data has evolved from a reference source into operational infrastructure, queried by automated systems, acted on by AI agents, and relied on for real-time decisions across the business, all of which places new demands on the platform supporting it.

The May '26 release prepares Oomnitza's platform infrastructure for how asset data is actually being used today. It makes integration operations more visible, strengthens the foundations customers depend on, and begins extending Oomnitza's data into the AI assistants and agents that are changing how teams interact with their information.

What’s New at a Glance

Integration Operations

Platform Infrastructure

Early Access Program

>> Skip to the end to watch the May '26 Release On-Demand Webinar 

Integration Operations

Monitor integration health across every object and connector

The existing monitoring dashboard for integrations covered only Asset and User objects, so failed syncs, stalled flows, or outdated records for IdPs, financial integrations, and custom objects were often discovered only after downstream impact.

The dashboard now supports any or every object across every platform connector, with real-time sync status, error counts, last update times, next scheduled run, filtering, and enhanced status indicators. 

Integration-health_ dashboard.png

Business Value Delivered

  • Audit Readiness: Creates a clearer record of integration health and sync history across the platform
  • Information Security Oversight: Surfaces integration disruptions that could indicate misconfiguration or credential issues
  • Continuity of Operations: Identifies failed syncs and stalled flows before they affect downstream systems

See Creating dashboards to monitor integrations

Receive proactive alerts when integrations fail or stall

Without proactive alerts, customers often didn't discover failed turnkey integrations or SMI processes until missing data had already affected operations.

Automated email and in-app alerts now fire when an integration fails or doesn't complete as expected. Users configure them by adding recipient contacts to the integration itself.

Integration-alerts.png

Business Value Delivered

  1. Information Security Oversight: Notifies teams quickly when credential or connectivity issues disrupt data flows
  2. Employee Experience: Reduces the operational burden of monitoring integration status manually
  3. Continuity of Operations: Shortens response time to integration failures, reducing downstream data risk

Ingest financial line item data with new turnkey connectors

Previously, financial integrations pulled in summary records along with linked line items, with no way to filter which line items were ingested. That made it harder to refine financial data for the use cases customers were targeting.

The new turnkey Coupa connector for purchase order and invoice line items now includes a filter customers can configure to control which line items are pulled into Oomnitza.

Business Value Delivered

  • Financial Accountability: Brings structured, filterable financial line item data into the platform for accurate cost attribution
  • Continuity of Operations: Reduces manual cleanup and remapping work for financial data

See Creating an extended integration for Coupa invoice line items and Creating an extended integration for Coupa purchase order line items

Expand and update turnkey connector coverage

The turnkey connector library continues to grow alongside customer demand. The May ’26 release adds new connectors and credentials and refreshes several existing ones based on feedback from the field.

New Credentials

  • IGEL (Session-Based)
  • Telia Company (OAuth 2.0)
  • Okta (OAuth 2.0 with JWT Assertion)
  • CyberArk EPM (Session-Based)

New Turnkey Connectors

Updates to Existing Connectors

  • SentinelOne: removed hard record limit
  • Google Workspace: added roles and role statuses to schema
  • Iru (formerly Kandji): updated user.email mapping label from “User” to “User Email”
  • Lucidchart Enterprise (SCIM) User Load: renamed to Lucidchart SCIM User Load (Groups as roles)

Platform Infrastructure

Restrict import log visibility by role

Import logs previously gave users high-level visibility into other users' imports, including initiator and record counts. Some customers raised concerns about this exposure of operational activity.

A new role-level privacy control restricts selected users to viewing only the results of imports they've performed themselves, reinforcing the principle that users should access only the data necessary for their role.

Business Value Delivered

  • Regulatory Compliance: Extends role-based access controls to import activity
  • Information Security Oversight: Limits exposure of operational data to only the users who need it

See Restricting the visibility of import logs. 

Build context-aware workflow wait conditions

Workflow wait blocks were defined statically in days, hours, and minutes, making it impossible to support advanced or context-aware automation.

Wait conditions now support dynamic calculation using global variables, workflow variables, record field values, and Jinja expressions. An offboarding workflow can revoke access immediately and then wait 30 or 90 days based on the user's title before completing full removal, consolidating logic that previously required multiple workflows.

Business Value Delivered

  • Regulatory Compliance: Enables policy-aligned timing in lifecycle workflows such as offboarding
  • Employee Experience: Reduces the workflow sprawl that operations teams have to maintain

See Wait Block

Performance improvements

A meaningful amount of work this release happened under the hood. These changes aren’t visible the way a new feature is, but they deliver lasting value.

Build Reliability and Deployment Consistency: Delivery tooling has been updated to create a more stable and repeatable deployment process from local engineering environments through testing and into production. The result is fewer deployment-related issues, lower downtime risk, and a smoother update rollout experience.

Credential Optimization: Connectors are now more performant thanks to improvements in how credentials are handled across paginated API endpoints. The change improves total sync execution speed, lowers API overhead, and creates a more reliable experience for the higher-volume integrations customers depend on.

Early Access Program (EAP)

Oomnitza’s Early Access Program gives customers early access to new capabilities before general availability and a chance to influence how those features evolve. EAP features are released to a limited set of customers so we can gather real-world feedback, refine the experience, and ensure the solution delivers meaningful value at scale.

Participants gain early visibility into new functionality, work closely with product teams, and help shape what reaches General Availability.

Oomnitza MCP Server

Asset and license data lives in the platform, forcing teams to manually answer questions and trigger workflows. AI copilots and external systems have lacked structured access, limiting automation and cross-system orchestration.

The MCP Server exposes asset data, searches, and workflows as secure tools for AI agents and enterprise systems. Copilots and integrations can query inventory, check compliance, and trigger lifecycle actions in real time. The server is compatible with any MCP-aware AI assistant, including Claude, ChatGPT, and customer-built chat agents.

Business Value Delivered

  • Employee Experience: Brings asset information into the AI assistants teams already use
  • Information Security Oversight: Provides structured, secure access with token-based authentication
  • Audit Readiness: Surfaces asset data in support of investigation and review workflows
  • Continuity of Operations: Extends the value of Oomnitza data across more enterprise systems

Please note: Feature documentation for the Oomnitza MCP Server will be accessible to customers in EAP and available to everyone when moved to General Availability.

To inquire about joining this EAP, contact your Customer Success Manager.

Asset Dependencies 

Modern IT environments are deeply interconnected, but teams often lack clear visibility into how assets depend on each other. When outages occur, response slows as teams fall back on tribal knowledge, static diagrams, or incomplete CMDB data.

Asset Dependencies makes asset relationships visible. By continuously tracking how assets connect and the criticality of each relationship, teams can instantly understand impact, assess risk, and see the full blast radius of a change. 

Asset-dependencies.png

Business Value Delivered

  • Employee Experience: Replaces tribal knowledge and static diagrams with current, queryable relationship data
  • Information Security Oversight: Surfaces dependency context that informs security and change decisions
  • Audit Readiness: Documents critical relationships between assets in support of operational reviews
  • Continuity of Operations: Helps teams anticipate the impact of changes and incidents across connected assets

Please note: Feature documentation for Asset Dependencies will be accessible to customers in EAP and available to everyone when moved to General Availability.

To inquire about joining this EAP, contact your Customer Success Manager.

Watch the On-Demand May '26 Release Webinar 

Related articles

Comments

0 comments

Article is closed for comments.