Skip to main content

Upcoming changes

This section lists planned feature releases as well as advance notices about updates that may impact existing functionality.

We recommend checking here regularly to stay ahead of any changes that could affect your setup.

Planned releases

The features listed below are planned for release in the coming months. This information is provided to give you an early look at what’s coming. Release timelines may change, but we aim to keep them as accurate and up to date as possible, with regular updates.

February 4, 2026

IMPROVED ADMIN Improved permissions management experience

We’re introducing a refreshed permissions management experience that improves how administrators view and manage access across the platform.

This release includes:

  • A single, consolidated admin interface for viewing, granting, and managing permissions within Admin & Settings.

  • A new permissions interface that replaces checkbox-based controls with a chip-based model, making it clearer and easier to grant or remove permissions across users and teams.

  • An updated central authorization service that supports the new permissions experience.

While this update focuses on improving clarity, consistency, and usability for administrators, the underlying permission model remains unchanged:

  • There are no changes to permission behavior, access levels, or role definitions.

  • Existing user access remains exactly the same.

To learn more about managing your user permissions, see: Managing permissions.

A screenshot of how you can manage service level permissions in the Celonis Platform.

February 2026

IMPROVED PROCESS DESIGNER Bugfixes

This release focuses on "under-the-hood" excellence and highly requested fixes for escalated customers:

  • Improved loading speeds for the Orphan view

  • Enhanced security and data consistency across the platform

UI updates:

  • Added alphabetical sorting for corona objects (to improve searchability)

  • Resolved the "grayed out" Refresh button issue

  • Added CPM scope filters for Organizations (to improve data control)

IMPROVED STUDIO Visual enhancements for View components

We’ve refreshed several View components with visual and functional updates to improve the look, feel, and usability of your dashboards and applications. These changes reduce wasted space, standardize the UI, and add new customization options for greater information density.

The highlights include:

  • Optimized KPI values: KPI values now scale to utilize more of the space available within the component.

  • Cleaner clickable KPIs: We removed wasted space around the clickable elements in clickable KPI list variation, and the unnecessary arrow was removed, resulting in a cleaner look and better space utilization.

    For example, this was the previous clickable KPI:

    KPI_list_example_before.png

    And with the visual enhancements:

    KPI_list_example_after.png

  • Removing unnecessary text: For the KPI Card, the "Related KPI" title is now only shown if trends are also enabled. When no trends are present, the title is removed to allow more space for the KPI values.

  • Reduced space between component and header: Many components had excessive spacing between the component and the header text. This has been reduced and standardized across all components.

    For example, this was the previous chart component:

    before_improvements.png

    And now with the visual enhancements:

    after_improvements.png

Breaking changes

The following updates introduce changes that may not be fully compatible with previous versions.

We’re providing this information ahead of time to help you prepare and make any necessary adjustments before the updates roll out.

March 31, 2026

BREAKING ADMIN Decommissioning API and application keys: Action required before March 31, 2026 [new date]

Important

These changes affect users who currently use API keys and/or application keys for the Audit Log, Platform Adoption and Team Login History APIs.

If you don’t use APIs or application keys in your applications or in third-party systems for these APIs, these changes will not affect you and no action is required.

Why we’re making these changes

We’re moving away from using API and application keys to the OAuth 2.0 authorization standard to provide a more secure, streamlined and efficient developer journey.

Users currently generate long-term API keys or application keys in the Celonis Platform. These keys are then embedded in applications and allow data to be requested or pushed using Celonis APIs. As these keys typically have a long life, cannot be rotated and their scope cannot be limited, any application with an embedded API or application key can access almost all Celonis APIs.

With OAuth 2.0, scoping means OAuth-enabled clients can access permitted APIs only. This follows the security principle of least privilege so an OAuth client only has the privileges required to perform a certain task.

Action required before March 31, 2026

  1. Identify any systems and/or applications that use API or application keys to call any of the following APIs:

    • Audit Log API.

    • Platform Adoption API.

    • Team Login History API.

  2. Migrate these systems and/or applications to OAuth 2.0.

    Additional points to consider:

    • If you were part of the beta program of the Platform Adoption Monitoring App and you're still using AppKeys, you must migrate to OAuth 2.0.

    • If you use the Celonis User Adoption dashboards, which extracts Platform Adoption data through Action Flow, you must migrate to the new Celonis Platform Adoption Monitoring App.

    • If you build your own Platform Adoption Extractor using the Celonis Platform Adoption Template and you selected AppKey as the authentication method, you must migrate to OAuth.

    • If you use Celonis Platform Adoption Monitoring App V1.3, no action is required. This version already uses OAuth.

    • The Platform adoption statistics under Admin & Settings will continue to work. No action is required.

For information on enabling OAuth 2.0 on the Celonis Platform, see Using an OAuth 2.0 token in Celonis.

Note

In future, we're aiming to move to OAuth 2.0 for all Celonis use cases. If you're using other Celonis APIs that already support OAuth 2.0, you can move to OAuth 2.0 for these APIs too. We’re also adding OAth 2.0 support for Action Flows and on-premise clients and will let you know when this is available

December 31, 2026

BREAKING DATA INTEGRATION Deprecating SAP on-prem extractor: Action required before December 31, 2026

Celonis is fully deprecating and discontinuing support for the SAP on-premise extractor (OPE) by the end of December 2026. All data pipelines currently relying on OPE will cease to function on this date.

Important

To ensure continuity of data flow, all customers using OPE must migrate to the modern On-Premise Client (OPC) by the end of December 2026.

This change is driven by a necessary update to our authentication security model. The outdated key-based authentication mechanism used in OPE is being replaced by the industry-standard OAuth protocol in OPC. To align with modern security requirements and maintain data pipelines, the entire legacy OPE framework will be shut down by the end of 2026. Any SAP Extractor running on the OPE after this date will stop working.

We recognize that some customers rely on specific OPE features which are not yet available in the OPC. These features are currently under development and we plan to deploy them in Q4 2025. We will communicate the exact release dates for these features in our Release Notes.

The following OPE features are currently not yet fully supported by the OPC:

  • Extraction via PI/PO

  • Extraction from legacy SAP versions 4.6 and 5.0

  • Column value filter functionality

  • Calculated columns