Last Updated: November 10, 2026
The incident workspace now includes updated and new widgets, customizable via the Incident Workspace Builder. Each widget can be expanded or restored to their default size using their
To give a widget the whole workspace, select Expand in its top-right corner. The widget fills the workspace; select Collapse in the same corner to put it back.
Adversary Lifecycle
The Adversary Lifecycle widget displays tactic and technique details specific to the current incident, providing clear and comprehensive insights for each item.
Reading a Technique in Full
The technique cards show a shortened description. Select a technique card to open a window with the tactic and technique name and the full description. Select Close to return to the widget.
Clicking on the
Conclusion
Users can use the Conclusion widget to record a summary for the incident's resolution using an HTML editor.
-
To edit the content, hover over the widget and click on the
icon.
-
To clear the HTML widget, hover over the widget, click on the
icon, then click on the Clear button.
Custom Fields
The Custom Fields widget allows users to add custom fields and values to incorporate information about the incident beyond what appears in the header panel.
To add a custom field, click on the
Description
The Description widget enables users to add or update the incident description using an HTML editor.
-
To edit the content, hover over the widget and click on the
icon.
-
To clear the HTML widget, hover over the widget, click on the
icon, then click on the Clear button.
Events Summary
The Events Summary widget provides summaries of events linked to the incident, including their linkage method, event ID and name, risk level, occurrence and last updated dates, and a link to access the event details pop-up window for linked events.
Showing More or Fewer Event Fields
-
Each event lists its fields under Event Summary. Select Show Less to shorten the list, and Show All (n) to show every field again.
-
Select the arrow at the right of an event to collapse its details to one line, and select it again to expand them. Selecting the Escalation Method row collapses or expands every event in that group the same way.
Files
The Files widget allows users to upload files to the incident using a drag-and-drop interface, or with Browse files. The widget notes: "Support for a single or bulk upload. Maximum file size: 30MB."
Findings
The Findings widget enables users to view, add, and edit investigation findings directly from the Overview tab. The data displayed in this widget mirrors the information in the Findings section of the Investigation tab.
Forensic Evidence
The Forensic Evidence widget keeps the incident's forensic evidence, with a chain of custody for each evidence item. See Forensic Evidence.
HTML
The new HTML widget allows users to dynamically add custom HTML content, allowing the display of richly formatted information.
-
To edit the content, hover over the HTML widget and click on the
icon.
-
To clear the HTML widget, hover over the HTML widget, click on the
icon, then click on the Clear button.
Incident Form
The Incident Form widget allows users to add or update information about the incident using the incident forms associated with the incident. For details on creating and filling out an incident form, refer to Creating an Incident Form and Filling Out the Incident Form During an Investigation, respectively.
Investigation Team
The Investigation Team widget displays users assigned to work on the incident and their access level. It also allows users to edit the team.
JSON Table
The JSON Table widget allows users to add a table containing custom JSON data into the incident. This data can be used as input for playbook tasks that support dynamic values.
Linked Artifacts
The Linked Artifacts widget enables users to associate artifacts with the incident. Users can click on either the
Acting on a Linked Artifact
-
The Action column holds the row's actions: Execute Command on every row, and Unlink Artifact on some rows. Hover over an icon to see its name.
-
Long artifact names are shortened with an ellipsis. Hover over a shortened name to see the full value.
After linking artifacts to the incident, users can access their details and execute commands on them. Linked artifacts are also displayed in the Link Analysis tab.
Linked Incidents
The Linked Incidents widget enables users to associate the current incident with other incidents. It has the Linked and Suggested Matches tabs. It presents a structured list that includes the incident number, title, type, status, creation date, owner, and associated artifacts.
Hovering over the owner icon, the text after "Created On", or any artifact reveals a tooltip with additional details.
-
To copy a linked incident's URL, hover over that incident and click on the
icon.
-
To unlink an incident, hover over that incident and click on the
icon.
-
To navigate to the linked incident, click the
icon.
-
To see a summary of the linked incident, click the
icon.
Notes
The Notes widget displays all notes associated with the incident. It also enables users to add new notes and perform keyword-based searches using Search notes. The All Notes, All Tags and Newest First menus filter and sort the list.
Filtering and Sorting Notes
-
Select All Notes to open the note-type menu: All Notes, Incident Note, Task Note and Morpheus AI Note.
-
Select All Tags to open the tag menu. It lists the tags on the incident's notes, each with a checkbox, with Search tags, Select all and Clear.
-
Select Newest First to switch the order to Oldest First, and select it again to switch back.
Playbook Automation
The Playbook Automation widget is the incident's record of its playbook runs: a timeline, newest run first, that shows which runs failed, which are still running and which are waiting on a task, so you can spot a run that needs attention without opening each one. Runs can be filtered, expanded in place and unlinked from the widget. The + button in the widget header adds playbooks to the incident, with bulk selection, filtering of custom or built-in playbooks, and filtering by integration commands used within playbooks.
Reading the Timeline
The timeline lists every playbook run on the incident, newest at the top. The time at the left of each run is when it started, shown in the time zone named at the top of the widget (for example, Times in PST); hover over a time to see the full date and time. A date is shown under the time whenever the timeline moves to another day.
Each run shows the playbook's name and its number of tasks. A run that needs attention says why on a second line, so you can read the problem without opening the run:
|
What you see |
What it means |
|---|---|
|
Failed: followed by task names, and a chip such as 2 failed |
Those tasks failed in this run. |
|
No task completed |
Every task in the run failed. |
|
Waiting: followed by task names, and a chip such as 1 waiting |
The run is held at those tasks, for example a manual task waiting for someone to complete it. |
|
A Pending, Running, Error or Done with errors chip |
The run's status. Runs that finished cleanly show no chip. |
|
nested beside the name |
A playbook started by another playbook. |
Back-to-back runs of the same playbook that all finished without errors share one row, so a playbook that runs many times does not push everything else down the timeline. The row reads, for example, 3 tasks each · ran 3×, and its time shows the newest run with "from" and the oldest run's time under it. Select the row to list each run with its own time, All Done, its number of tasks and its own Open full run and Unlink playbook icons.
A run that fails, is still running or is waiting is never grouped; it always has its own row.
An incident with no runs shows No playbooks have run on this incident, with a pointer to the control that adds one.
A grouped row expanded
Filtering the Timeline
The filter at the top of the widget narrows the timeline to the runs you are looking for. Each option shows how many runs match it.
|
Filter |
Shows |
|---|---|
|
All |
Every run. |
|
Errors |
Runs with at least one failed task. |
|
Running |
Runs that are still running. |
|
Waiting |
Runs held at a task, such as a manual task. |
The time range selector beside it limits the timeline to All time, Last 24 hours, Last 7 days or Last 30 days. The counts follow the time range. The widget opens on All and All time.
With Errors selected, a line under the timeline says how many runs completed without errors and are hidden by the filter. When nothing matches, the widget says so (for example, No runs with errors or No runs in the last 7 days) and offers Show all runs or Show all time to clear the filter or the range.
Opening a Run's Details
Expanding a run shows what it did without leaving the incident, so you can check a failed task or see what is left to run before deciding whether to open the full run.
-
Select the run, or the arrow at the right of its row.
-
Select it again to collapse it.
RESULT
The run expands in place and shows:
-
Description: the playbook's description, or No description available.
-
Integrations: the integrations the playbook uses, when it uses any.
-
TASKS, with a count by state (for example, TASKS · 4 DONE · 1 ERROR), above a table of TASK ID, TASK NAME and STATE. The table shows the first five tasks in the order they ran; select the line below it, which counts the tasks not shown (for example, 6 more tasks: 4 done · 2 running), to show the rest, and Show fewer to hide them again. For a very long run, the last line says how many more tasks there are and opens the full run to see them.
-
Open full run, which opens the run in a window, and Unlink playbook.
A run expanded in the timeline
READER NOTE
Unlink playbook appears only where unlinking playbooks is allowed and you can edit the incident. A nested playbook cannot be unlinked on its own; its details read Nested playbooks cannot be unlinked.
Selecting a run in the timeline expands its details in place (see Opening a Run's Details). To open the run itself, select Open full run on a hovered or expanded run: a window opens with the executing playbook, identical to accessing it via the Playbooks sidebar menu.
Recommendations
The Recommendations widget enables users to view, add, and edit analyst recommendations directly from the Overview tab. The data displayed in this widget mirrors the information in the Recommendations section of the Investigation tab.
The process of adding a recommendation, whether with a data table or HTML Rich Text, is identical to adding a finding, with the exception that the category dropdown is available only for findings.
Remediations & Mitigations
The Remediations & Mitigations widget enables users to view, add, and edit analyst remediation and mitigation strategies directly from the Overview tab. The data displayed in this widget mirrors the information in the Remediations & Mitigations section of the Investigation tab.
The process of adding a remediation and mitigation strategy, whether with a data table or HTML Rich Text, is identical to adding a finding, with the exception that the category dropdown is available only for findings.
Investigation Summary
The Investigation Summary widget mirrors the content of the Summary section found in the Investigation tab of the sidebar. All incident summaries are auto-generated at the time of incident creation. Users can edit the summary by clicking the edit icon and delete it by clicking the trash icon, both of which appear on hover.
Tasks
The Tasks widget provides a clear view of completed, upcoming and overdue playbook and ad hoc tasks. It also includes a graphical progress bar to visually track completion.
Finding Tasks in the Widget
-
Select Assigned to Me for your own tasks, or Assigned to Others for everyone else's. Each tab has its own progress bar, for example 1 of 9 tasks pending and 89% Done.
-
The progress bar is also a filter. Select its green part (the done tasks) to list the COMPLETED TASKS.
-
Select its orange part to list the PENDING TASKS again.
-
Select the filter icon to open Filters: Assignee, Task Type, Playbook Status and Show Overdue only.
-
Select Latest Due to choose the Due Date order: Latest Due or Earliest Due.
Users can click the