Skip to main content

Celonis Product Documentation

General differences

Process Analytics


Create, edit, and publish Analysis

Create, edit, and publish View, Analysis, Skill, Knowledge Model, Data Explorer, Simulation, and Action Flow

Organize content in workspaces

Organize content in spaces, packages, and folders

Connect to one data model per workspace

Connect to n data models per package

Navigate to analyses by returning to the home page

Navigate to analyses directly using the side panel

Publish analyses individually

Publish the whole package

Previous analysis versions are overwritten when publishing and cannot be recovered

Package level version control

Content CLI (Command Line Interface) is not supported

Manage content using Content CLI with Git integration for advanced version control

Marketplace content is not available

Download best practice analyses, apps, connectors, Action Flow templates, and experiences from the Marketplace

Studio as a platform

Process Analytics and Studio are separate services that both host the Analysis you are already familiar with. In Studio, the Analysis can be connected not only to a Data Model like in Process Analytics, but also to a Knowledge Model.


In addition to the Analysis, a number of other assets are available in Studio:


Used for

image32.png - Analysis

Ad hoc analysis, conformance checking

image5.png - Views

Operational tasks, monitoring, executive dashboards

image36.png - Knowledge Model

Central storage of business knowledge and definitions

image31.png - Action Flow

Workflow automation

image10.png - Skill

Workflow automation (legacy)

image3.png - Data Explorer

Data validation and exploration

image24.png - Simulation

Simulate the impact of hypothetical process changes on KPIs

Content organization

There are three main differences in how content is organized in Process Analytics vs. Studio:

  1. The levels on which content can be organized in the Studio hierarchy in ascending order of granularity are space, package, and asset. The Process Analytics workspace corresponds to the Studio package.

  2. Unlike in Process Analytics, there is no restriction in Studio that every asset in a package must be connected to the same data model.

  3. You can further organize assets within a package into different folders, nested up to nine times. Permissions cannot be assigned to folders.

As a result, content organization is more flexible in Studio. What may have been accomplished in Process Analytics using tags or clunky naming conventions can be accomplished in Studio more neatly using spaces and folders.

Examples of how to group content
  • By process (P2P, O2C, AP, AR)

  • By department or business unit (Finance, Procurement, HR)

  • By region (NA, EMEA, APAC)

  • By use case (On Time Payment, Manual Rework, Stockouts)

  • By development lifecycle (Dev, QA, Prod, Archive)

For more information, see How can I structure my content inside Celonis Spaces?.


Developing content and viewing content are done in two separate areas, which you can access via the EMS navigation bar on the left:


As an analyst or admin, edit and publish content by clicking Studio.


As a member, view published content by clicking Apps.

Content navigation

In Studio, you have direct access to all content via the navigation panel on the left, while also being able to work with the selected content on the same page.


Studio provides a development process that is simple, scalable, and worry-free. Native version control allows you to track and restore previous package versions.

Since assets can depend on one another in Studio, publishing is done on a package level rather than on an asset level. To publish the current package, you can click the Publish Package button at the top right. image40.png

If you want to publish only the changes made to an individual analysis, you can still do so by de-selecting all other items in the menu that follows. The result will be considered a new version of the package.


For more information, see Publishing and Versioning.

Content CLI & Git integration

In Studio, you can move or copy content between packages, spaces, and teams using the graphical interface. Additionally, the command line interface allows you to pull, push, and update Studio content from your local machine. This is for advanced users who need to manage content programmatically at scale.

Usage examples of content CLI
  • Move content between teams

  • Automatically sync a sandbox and productive team

  • Manipulate content by editing JSON files in your local IDE

  • Integrate with Git for advanced version control and approvals

  • Create data backups

For more information, see Content-CLI as a content management tool in the EMS.


The Marketplace is where you can install pre-built content from Celonis and our partners. Marketplace content is for Studio only and is not compatible with Process Analytics.