Customizing the Incident Workspace

Last Updated: November 10, 2026

Overview

The workspace layout of an incident type decides which widgets its incidents show. Besides the built-in widgets, two widgets hold content that your own playbooks write: the Markdown Widget ("Custom Markdown content for an incident") and the HTML Widget ("Custom HTML content for an incident"). Add one to a workspace, give it a name, and point a playbook at its field name. Analysts can also edit a Markdown widget's content by hand on the incident (see Editing a Markdown Widget by Hand below).

Workspaces are built for each incident type. To open the builder, assign a workspace and save it, see Configuring an Incident Type: Incident Workspace. For every widget the builder offers, see Incident Workspace Widgets.

Adding a Markdown or HTML Widget

READER NOTE

The Markdown widget is off by default and is turned on by D3 Support. Until it is on, it cannot be added to an incident layout. Contact D3 Support for assistance.

  1. Go to Configuration > Incident Type Manager and select the incident type. See Incident Type Manager.

  2. Select Incident Workspace, then open a workspace with ⋮ > Edit, or select New Workspace.

  3. In Widgets, type Widget in the search box. The list shows HTML Widget and Markdown Widget.

  4. Drag Markdown Widget or HTML Widget onto the canvas.

Result: The widget reads "To add or update Markdown content using playbook commands, use the following field name." (or HTML content), followed by its field name, CustomMarkdownWidget or CustomHtmlWidget, and a copy button.

Markdown and HTML widgets in the builder

The workspace builder with a Markdown Widget and an HTML Widget on the canvas, each showing the field name that playbooks write to, and the two widgets in the Widgets list

Resize and move the widget like any other, then select Save at the top right of the builder.

Naming the Widget

When you add the widget, its title opens in a box with ✓ and ×. Type a name for it and select ✓.

Naming a new widget

A newly added HTML widget with its title box open, the new name Analyst Briefing typed in, and the check mark that applies it

The field name follows the title. A widget named Analyst Briefing gets the field name CustomAnalystBriefing.

The new field name

The renamed widget, Analyst Briefing, now showing the field name CustomAnalystBriefing

The ? beside the field name explains: "This field name is automatically generated based on the widget name and can be used to configure Markdown content in playbooks. Renaming the widget re-derives this field name, so keep the title in step with whatever writes the content (for example an APD output section of the same name)."

How the field name is made

c03-field-name-tip.png

Filling the Widget from a Playbook

A playbook writes the widget's content to its field name. The ⓘ beside playbook commands lists what to use:

Playbook

Use

Preprocessing playbook

The Escalate task, or the commands Create Incident and Create Incident With Conditions

Investigation playbook

The commands Set Incident Fields and Set Incident Fields In Bulk

Which playbook commands to use

c02-playbook-commands-tip.png

Select the copy button beside the field name to copy it into the command or task. For building the playbooks themselves, see Investigation Playbooks and Preprocessing Playbooks.

Editing a Markdown Widget by Hand

A Markdown widget can be edited by hand on the incident, so an analyst can correct or add to what a playbook, an integration or APD wrote without leaving the incident. The edit is saved to the widget's field, the same field name that playbooks write to, and the widget then shows the new content. The same editor is in the classic view.

Editing needs the Edit Incident privilege. A closed incident also needs Edit Closed Incident. Both are set per role under Operational Modules > Incident. See Roles.

  1. Open the incident and go to the workspace page that holds the Markdown widget.

  2. Hover over the widget and select the pencil icon at its top right.

An empty widget reads "No content yet. Click on the [pencil icon] to edit contents", and its pencil icon opens the editor too. The pencil icon does not appear while the widget's content is still loading, or when what was written to the field is not text.

  1. On the Write tab, edit the widget's Markdown. Select Preview to see how it will look.

A Markdown widget in Edit Mode

A Markdown widget in Edit Mode with the Write and Preview tabs, the overwrite warning and the check icon that saves
  1. Select the check icon to save.

Result: The widget shows the new content, and the message "widget name updated successfully" appears.

To leave without saving, select ×. If you changed anything, D3 asks "You have unsaved changes. Are you sure you want to cancel?"; select Yes to discard the changes. If a save fails, the editor stays open with your text, so nothing you wrote is lost.

To empty the widget, hover over it and select the bin icon beside the pencil icon (shown only when the widget has content), then select Clear.

A later automated write replaces a manual edit. The editor says so beside its tabs: "Can be overwritten by APD, an integration or a playbook". Hover over the warning for the detail: "If an APD escalation, an integration or a playbook writes this field again, your edit will be overwritten."

Other Widgets You Can Add