---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/now-intelligence

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Playbook project

# Create a project using Playbook data {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Use Process Mining to analyze Playbook executions and identify bottlenecks in your workflows. Process Mining works alongside Playbooks configured in Workflow Studio. By analyzing execution logs generated during playbook runs, Process Mining enables post-execution visibility into how human agents are handling customer incidents.

## Vorbereitungen

Role required: pd_author, pd_operator, sn_process_mining_analyst, sn_process_mining_power_user, or sn_process_mining_admin. You must have the playbook.write roles.

## Warum und wann dieser Vorgang ausgeführt wird

Playbooks are built and configured in Workflow Studio, where you define activities for human agents and set up decision logic based on customer scenarios. When agents execute these playbooks, the system generates execution
logs that Process Mining can analyze.  
Hinweis:  
Note the following:

* Only one playbook can be analyzed at a time.
* The Analyst workbench provides basic analysis and bottleneck identification only.
* Summary insights, improvement opportunities, and detailed phase information aren't yet available.
{#playbook-project__ul_hbl_hnx_k3c}

## Prozedur

1. Navigate to WorkspacesProcess Mining Workspace.
2. Select Create New Project from the projects page.  
   The Set objectives tab is displayed.
3. Provide details on the Set objectives tab.

   | Field | Description |
   | Select type | Select <kbd class="ph userinput">Project</kbd>. |
   | Name | Provide an intuitive name for the project that you're creating. |
   | Short description | Provide a short description for the project you're creating. |
   | Source Type | Select <kbd class="ph userinput">Playbook</kbd> from the list. |
   | Playbook | Select a table with playbook data from the list. |
   | Mark as restricted | Select the check box if you want to limit project access to the owner and the users they explicitly share it with. Administrators and power users don't have access to the mined data unless the project is shared with them. Once a project is marked as restricted, only the owner can clear this field. When you're dealing with sensitive data and must restrict access, you can use this option. |
   | Auto retire | This field is available only if you choose the type as Project. Select the Auto Retire check box if you want to retire the project automatically based on inactivity for a specified number of days (Default: 90 days). You can extend the retirement by moving it back to published or draft state before the versions get cleaned in another 90 Days (default). If you don't change the retired status within the specified days, the mined versions are permanently deleted. However, the project definition isn't deleted. You can opt out of auto retirement by clearing this check box. The default value of 90 days can be changed by the administrator in the System Properties. For more information see, [Data cleanup properties](https://servicenow-prod.fluidtopics.net/K42venGdSWOc340KROnDcg#data-cleanup-properties "Set properties that determine how long Process Mining projects are maintained before being deleted by the scheduled cleanup job."). |
   |-|-|

   {#playbook-project__choicetable_akh_rrs_33c}
4. Select Create project.  
   The Scope your analysis tab is displayed. The filter conditions are preconfigured.  
   Hinweis:  
   There are no improvement opportunities for playbook projects. All conditions are preconfigured. You can't edit any condition.
5. Select Review and Mine.  

   The Analyst workbench provides execution metrics for completed playbook runs, including duration, average time per execution, and activity occurrence counts. The Analyst workbench visualizes parallel
   activities and decision points within the workflow to help you understand how playbooks are being executed.