Skip to main content

Celonis Product Documentation

Task Mining Team Insights

Added with Task Mining Client 2.8.1

Team Insights lets you calculate metrics for a subset of defined users, such as teams, regions, or roles. It is popular with analysts looking to:

  • investigate differences among a subset of users and locate root causes more granularity (e.g. on a team level) for harmonization, best practices or change management programs.

  • restrict access for analysts to view user data in a specific group, such as limiting team managers to only see the application usage for their team.

To protect the user's privacy, the users can be de-identified by applying pseudonymization filters.


Use case example

Company TenAce runs the largest IT transformation project in its recent history. They use Task Mining to support the program by providing additional insights to track success and pinpoint issues.

They have a hypothesis that certain teams are still using the legacy application rather than adopting the new tool. By drilling down into the application usage per team, the analyst can see that the “Buying Spain” team has fully adopted the new tool, whereas “Buying - USA” still relies on the legacy application. The analyst reached out to the USA team and learned that the new tool fails to support some specific corner cases. Using Task Mining the company could very quickly pinpoint the issue and identify the root cause.

Setup - Users provide input via User Attributes

The analyst configures the User Attributes so that the users who run the Task Mining Client have to select the team to which they belong during the initial setup of Task Mining.

User Attributes

These attributes define what you want to learn about your users. Users will have to provide this information before they can begin Task Mining. This data can help you to derive more insights. Examples include users being required to provide their team name, which can be used to investigate differences between teams while keeping single users de-identified.


User provided input is stored in the “user_interaction_event_log” table.

User Attributes Setup Guide
  1. Go to Task Mining > Your Project > Client Settings and select “Advanced Settings”.

  2. Download the configuration file.

  3. Open the configuration file in your Configuration Editor (Desktop application).

  4. Set the Custom1 column name to “Team” and then use the Values field to provide the options for the users to select.



    Please define adequate user attribute options so that users can still be kept de-identified:

    • Ensure that more than e.g. 5 users are in the team or per individual attribute value to keep users de-identified.

    • Please assess to add custom data pool permissions to hide users in groups with fewer than five users if required.

  5. Select the Field mandatory check box to make this a required field.

  6. Click OK.

  7. Ensure that the Custom1 attribute (and any others) are logged in the event processing rules by clicking the Event Processing Rules link on the left.

  8. Then for each of  your existing rules, click Edit -> Logging to verify that the attributes are selected for each rule.

  9. Save the configuration and upload it to the Advanced Settings.

  10. Click Save to apply the new configuration to all clients connected to this project.

    Clients will be updated within 5 minutes of coming online. The new User Attributes are checked during every startup of the Task Mining Client.

    If you want to manually apply the new User Attributes, open the Task Mining Client, go to File > Quit and then restart it.

  11. Now agent users are asked to provide the input the next time they start the Task Mining Client.

  12. You can also customize your analysis in Studio. For example, you can add a dropdown to filter values in the ‘user_interaction_event_log’.‘Custom1’ column, which contains the information provided by the user (team, region, role).

Data Privacy

Task Mining provides multiple features to protect the privacy of a Task Mining user. As data privacy legislation varies significantly between countries and use-cases, the solution is highly configurable. Following best practices are supported and shall be considered by the Task Mining admin during the setup of the Task Mining Client:

  • Limit data capturing to the minimum required for the specific use case, e.g.

    • Don’t use the capturing of screenshots if not required

    • Avoid capturing user input values, form values and free text input

  • Pseudonymized usernames and other fields that might contain the usernames

  • Restrict access to Task Mining data via data pool permissions

  • Adapt the information provided in the information screen

  • Define adequate user input options

You are advised to consult your data privacy experts before activating Task Mining for your users and also to support the implementation of Task Mining by organizational measures (e.g. internal communication, alignment with workers council - if applicable).