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.
DATA INTEGRATION Changes to Celonis IP addresses: Action required before 2025-05-15
Important
These changes affect the eu-2, jp-1, uk-1 and us-2 realms only. If you're on any other realm, these changes will not affect you and no action is required.
What's changing
We’re modernizing our infrastructure and the Celonis IPs as origin addresses used in eu-2, jp-1, uk-1 and us-2 are changing. Celonis IPs as origin are the source IPs used to access your on-premises services such as web services or mail servers or services in a SaaS provider tenant (such as Salesforce or Snowflake).
If you don’t take the action required before 2025-05-15, traffic originating from Celonis may be blocked, leading to connectivity issues with cloud databases and/or on-premises services including:
Cloud extractors if Celonis IPs as origin are included in security device allowlists.
Action Flows if any action modules use external systems that have their own IP address allowlists.
Machine Learning (ML) Workbench if traffic contacts data systems that have their own IP address allowlists.
Action required before 2025-05-15
Check if your systems have IP allowlisting configured for Celonis-originating traffic.
If:
Yes, add the IPs in the table to all allowlists for your realm, retaining the existing IPs for now.
No, no action is required.
IPs to be added to allowlists before 2025-05-15
Realm | IPs to be added before 2025-05-15 |
|---|---|
eu-2 | 20.31.2.184 20.31.2.185 20.31.2.186 |
jp-1 | 20.44.169.64 20.44.169.65 20.44.169.66 |
uk-1 | 51.142.213.244 51.142.213.245 51.142.213.246 |
us-2 | 20.99.152.112 20.99.152.113 20.99.152.114 |
Action required after 2025-09-17
Note
If your systems do not have IP allowlisting for Celonis-originating traffic, no action is required.
Check all system IP allowlists for your realm contain the IPs included in Celonis IPs as origin.
If they don't, see Action required before 2025-05-15.
Remove the IPs in the table from all allowlists for your realm.
IPs to be removed from allowlists after 2025-09-17
Realm | IPs to be removed after 2025-09-17 |
|---|---|
eu-2 | 13.73.158.49 13.80.109.60 168.63.109.207 |
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 |
DATA INTEGRATION Changes to Celonis IP addresses: Action required before 2025-04-22
Important
These changes affect the eu-3 realm only. If you're not on the eu-3 realm, these changes will not affect you and no action is required.
What's changing
We’re modernizing our infrastructure and the Celonis IPs as origin addresses used in eu-3 are changing. Celonis IPs as origin are the source IPs used to access your on-premises services such as web services or mail servers or services in a SaaS provider tenant (such as Salesforce or Snowflake).
If you don’t take the action required before 2025-04-22, traffic originating from Celonis may be blocked, leading to connectivity issues with cloud databases and/or on-premises services including:
Cloud extractors if Celonis IPs as origin are included in security device allowlists.
Action Flows if any action modules use external systems that have their own IP address allowlists.
Machine Learning (ML) Workbench if traffic contacts data systems that have their own IP address allowlists.
Action required before 2025-04-22
Check if your systems have IP allowlisting configured for Celonis-originating traffic.
If:
Yes, add 20.79.237.0/30 to all allowlists, retaining the existing IPs (20.218.91.128 and 20.218.105.182) for the eu-3 region.
No, no action is required.
Action required after 2025-09-17
Note
If your systems do not have IP allowlisting for Celonis-originating traffic, no action is required.
Check all your system IP allowlists contain the IP range 20.79.237.0/30.
If they don't, see Action required before 2025-04-22.
Remove the following IPs from all your system allowlists:
20.218.91.128
20.218.105.182
STUDIO EXPORT ALL service permissions added (2025-04-22)
We're introducing an enhancement to our Studio service permissions that gives admins granular control over exporting content (i.e. packages, assets) to other teams. The EXPORT ALL permission, managed from the Permissions area of Admin & Settings, gives users the following abilities:
Copy-To: The user can utilize the exporting functionalities copy-to to export package and asset configurations to other teams (i.e. instances).
This feature can be accessed from within Studio by clicking Options - Copy to:
Content-cli: The user can utilize the content-cli to export package and asset configurations.
Currently, users with EDIT permissions can export content without restrictions. When this feature is introduced, these users will receive EXPORT_ALL permission by default to reflect their current capabilities, so they won’t be affected by the migration. We recommend reviewing which users shouldn't be able to export content outside of their teams, and to proactively remove the EXPORT_ALL permission.
The EXPORT_ALL permission requires users to have EDIT permission to ensure proper access, without it, the content won’t be visible.
For more information about Studio service permissions, see: Studio service permissions.