Planned Releases
The features listed below will be released in the coming months. The information provides advance notification about new features. The dates are subject to change. However, we strive to keep the date information as accurate as possible, giving daily updates.
You can find information about released features in our Release Notes and documentation.
Tip
Use CTRL+F or Command+F to search for specific terms.
PROCESS NAVIGATOR and PROCESS DESIGNER - Reporting API (2025-09-05)
We're adding the ability to generate your own reports in Celonis Process Management. Admins will be able to generate an API key with CPM that can be used in to bring CPM data into 3rd party reporting tools, enabling analytics on process content created in Process Designer. Once the API is set up, analysts can use the data made available through the API to build reports.
STUDIO Legacy View component migration (2025-09-04)
With this release, you can migrate select Legacy View components to your Views, allowing you to add and further configure the components using the latest View editor and features.
While in Legacy View edit mode, hovering over a supported component allows you to copy that component (and its configurations) and then paste it into a Studio View. This migration works best when copying between Legacy Views and Views that use the same Knowledge Model, removing the need for you to reconfigure the data.
To view the full list of supported components and an overview of current limitations, see: Migrating Legacy View components to Views.
DATA INTEGRATION Inactive Data Model suspension (2025-08-28)
With this release, Data Models that haven't been referenced in PQL for 40 days or more will be suspended, preventing unnecessary load on the Celonis Platform. When a Data Model is suspended, the data can still be accessed through assets and PQL but the data is no longer up-to-date.
Once a Data Model has been suspended, you can then manually reactivate the load. When a PQL query then gets triggered, in can take up to an hour until the Data Model load restarts.
Before a Data Model is suspended, both Analysts with 'Manage Data Pool' permissions and the original creator of the Data Pool are sent email notifications informing them of an upcoming suspension. These notifications are sent seven days, two days, and then shortly before the Data Model is suspended.
DATA INTEGRATION Changes to Celonis IP addresses: Action required after 2025-09-17
Important
These changes affect the eu-2, eu-3, jp-1, uk-1 and us-2 realms only. If you're on any other realm and/or don't use IP allowlisting for Celonis-originating traffic, these changes will not affect you and no action is required.
Ensure all your system IP allowlists contain the IPs listed in Celonis IPs as origin.
Remove the following IPs from all allowlists in your realm(s).
Realm
IPs to be removed after 2025-09-17
eu-2
13.73.158.49
13.80.109.60
168.63.109.207
eu-3
20.218.91.128
20.218.105.182
jp-1
52.243.46.143
uk-1
51.132.48.184
us-2
20.187.3.129
52.183.80.180
40.65.121.189
Decommissioning API and application keys: Action required before 2025-12-31
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 2025-12-31
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.
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