Cockpit

To gain a full understanding of a technical problem you often need to inspect the process execution flow that happened before the error occured. For example, a technical expression at a gateway may have failed as 5 steps before that gateway, a variable was populated with a wrong value due to a design error in a DMN decision table that was invoked from a BPMN business rule task.

With Cockpit you can quickly discover such an error by inspecting

• the BPMN audit log of executed steps,
• the way process variables have been changed during those steps
• and the historic decision table executions to see which rules applied in the specific execution of that process.

Administrators use Admin to manage your users, organize them in groups and grant permissions. Camunda decouples the identification of users from their authorization to execute certain actions.

To complete identification, you can either use the user management system that ships with Camunda or your existing user management system that you can integrate with Camunda via LDAP. Once a user has identified themselves (e.g. submitted the login screen in a Camunda web application), Camunda will authorize them based on the permissions defined in Camunda Admin.

The permissions that you define in Camunda Admin will be considered at all levels, i.e. when calling the core engine API, the REST API and when using a Camunda web application.