Eligible playbooks
Playbooks that meet the following criteria can be submitted for execution:- They contain only action steps that have manual commands or parallel steps
- They do not have an validation errors
- They are not revoked
Who can see an execution
The second step of the Run Playbook dialog, People involved, ends with Who can see this execution:- Workspace (the default): everyone with access to the workspace can open the execution.
- Restricted: only the people on the execution can see it.
Who is on a restricted execution
Access follows the steps. Someone who is assigned a step later, or claims a team step, sees the execution from that moment. Someone who no longer holds any step, and is neither its owner nor seated in its war room, stops seeing it.
What a restricted execution is left out of
For everyone who is not on it, a restricted execution does not exist. It is left out of:- the execution lists of the workspace and the All Executions list across workspaces
- the Executions Overview, its numbers and its PDF report, and the workspace overview report
- the workspace task lists and the source playbook filter
- the improvement suggestions of the workspace
- the global search
- the answers of Cymph AI, which only reads the executions the person asking can see
- the organisation’s Slack or Teams channel: nothing about a restricted execution is posted there, since the channel reaches everyone. The people on it are still notified directly, in the app and on their own channels.
Executions started from a war room
An execution started from a war room takes the visibility of the room. The choice is shown locked in the dialog, and Cymph applies it whatever was selected.- The executions of a restricted room are restricted. The people seated in the room see them, along with the people holding their steps.
- The executions of a room open to the workspace are open to the workspace.
- When the room’s visibility is changed, its executions follow in the same moment, in both directions. People who lose access are dropped from the execution’s chat and calls.
- The room’s Executions tab lists the room’s executions for everyone who can open the room, guests included.
Limits to know
- The visibility of an execution is chosen when it starts and cannot be changed afterwards. Only an execution of a war room changes, by changing the room.
- A completed exercise updates the last tested date of its playbook, and a restricted one does too. Everyone who sees the playbook sees that it was exercised and when. The note next to the date reads “Execution: restricted” and does not name the execution. Operational executions never change the last tested date.
Execution editor
Execution editor is the central place where all major actions for an execution happen. It is split into three major areas:- Global status and actions panel: this panel resides on the left side and contains information about the execution, allows you to view and add global notes and attachments and see an overview of the assignees
- The top action bar which contains options to view and ad global notes, view and add global attachments, see an overview of the assignees, the status and duration of the execution, see the source playbook and finally see the action log.
- The workflow panel. This is the panel where the steps of the execution are visualised. From here, you can change the status of each step as long as it is assigned to you or change the assignee for a non-completed step as long as you are the execution owner

Initial assignees
When submitting a playbook for execution, the assignees of each step in the source playbook will be respected. If no user is assigned in the source playbook or the assigned user is not found, the execution owner will be assigned to that step.Timers
An execution has two kinds of timers:- A global timer for the execution as a whole, defining how long the entire procedure is expected to take.
- Step timers, one per step, defining how long each individual activity is expected to take.
Changing step status
In order to change status of a step you must be assigned to it. Changing status can be done in two ways:- Via the status dropdown menu of the status node

- Click on a node to show the details panel and change the status from the dropdown menu there

- Not Started
- Planned
- In Progress
- In Review
- Skipped
- Failed
- Completed

Allowed status transitions
The table below summarised the allowed transitions among statuses.Changing step assignee
If you are the execution owner, you can change assignees of a step as long the step has not finished (skipped, completed, failed, canceled) You can change a step assignee in two ways:- By clicking on the avatar icon of the current assignee in the step node and selecting a new one

- By clicking on a node and change the assignees from the Assignees tab of the step details panel

Adding notes to a step
- Click on a step and its details panel will appear
- Navigate to the Notes tab
- Enter your note text and click on Add Note to add it

You can add notes at any time, independent of the step and the entire execution status
Deleting a step note
If you are the author of a note, you will be able to delete it.- Click on the step in order for its details panel to appear
- Navigate to the Notes tab
- Click on the delete icon of the note you want to delete
- Select Remove on the confirmation dialog that appears

Editing a step note
- Click on the step in order for its details panel to appear
- Navigate to the Notes tab
- Click on the edit icon of the note you want to edit
- Edit the note contents and click on Save to save your changes

Managing step attachments
If you want to add an attachment:- Click on the step in order for its details panel to appear
- Navigate to the Attachments tab
- Click on Add Attachment and select a file to add


You can upload any file type as an attachment. Maximum file size is 20MB.
Managing global notes
Adding, editing and deleting global notes (notes for the entire execution) is similar to managing step notes. By clicking on the Notes button either from the global action panel on the left or from the top action bar, the Execution Notes drawer will open.You can add notes at any time, even if the execution is complete.
Managing global attachments
Adding, editing and deleting global attachments (attachments for the entire execution) is similar to managing step notes. By clicking on the Attachments button either from the global action panel on the left or from the top action bar, the Attachments drawer will open.You can add attachments at any time
Canceling an execution
If you own an execution and if the execution is in progress, you can cancel it anytime. In order to cancel an execution:- Click on the More Actions button from the top action bar

- From the dropdown menu that appears click on Cancel Execution
- Provide a reason for cancellation in the dialog box that appears
- Click on Mark Execution as Canceled to cancel the execution

Executions Overview
A high-level summary of all playbook execution activity, including status distribution, performance insights, and per-playbook/step metrics.Executions Distribution by Status
This section presents a donut chart summarizing the total number of executions and their current statuses.- Total — The aggregate count of all executions (e.g., 8).
- Status breakdown (shown as colored legend items):
- 🔵 In Progress — Executions currently running (e.g., 50%).
- 🔴 Canceled — Executions that were manually stopped before completion (e.g., 12%).
- 🟢 Completed — Executions that finished successfully (e.g., 37%).
- Manual — Executions started by a user, showing a count and percentage of total (e.g., 8 / 100%).
- Automated — Executions triggered automatically by a rule or scheduler (e.g., 0 / 0.00%).
Insights
The Insights section displays key performance metrics calculated only across completed executions (i.e., those not currently in progress). It contains four metric cards:
Clicking on a linked playbook name in any of the Insights cards navigates directly to the relevant execution detail.
Performance by Playbook
A paginated table ranking playbooks by execution duration, sortable via the Sort by dropdown (e.g., Slowest to Fastest).
Pagination controls (‹ page indicator ›) appear below the table when there are multiple pages of results.
Performance by Step
A paginated table ranking individual playbook steps by average execution time, also sortable via a Sort by dropdown.
Pagination controls allow browsing through all steps (e.g., page 1/2).
Execution List
- Navigate to the Playbook Executions page
- Click on Playbooks from the left menu
- Select Playbook Executions from the navigation sidebar

- Click on Group By Status button
- Executions are grouped by status

Executions across all workspaces
The executions navigator also has Across All Workspaces → All Executions. It lists every execution you can see: those of each workspace you are a member of, and those you hold a step in anywhere else. A Workspace column says where each one ran. Restricted executions appear only if you are on them. Automated executions, which ran in a system connected to a workspace such as a SOAR, are listed too, for the workspaces you are a member of. They are read live from each connected system, so the list can take longer to load when several workspaces have one; a system that does not answer leaves its executions out. The filters that mean the same in every workspace are available here (name, status, purpose, who ran it, type, playbook source, execution source, source playbook, dates and KPI adherence). Actions on a row follow your permissions in the workspace the execution ran in.Tasks Overview
- Navigate to the Execution Tasks page
- Click on Playbooks from the left menu
- Select Execution Tasks from the navigation sidebar
- Overview: in this view, you will be able to see at a quick glance your tasks, their status and the recently assigned tasks to you

- My tasks: this view is a list of tasks assigned to you. You can also group by status to see the tasks grouped
- Assigned By Me: this view is a list of tasks that you assigned to either you or other users. You can also group by status to see the tasks grouped


