Playbooks
A playbook is a numbered response sequence for a repeating situation — a security incident or a remediation run — that a person works through while Aegis records how far it has got.
A playbook (a tracked list of response steps for a repeating scenario) holds an ordered set of steps and a completion percentage. It is not a procedure, which is a standing document you author, version and put through approval. A playbook is bound to one piece of work: opened when something happens, worked through step by step, then completed or cancelled. Aegis can draft the sequence for you, but nothing reaches the record until a person has read the draft and applied it.
Who uses it
The screen sits behind the PLAYBOOKS module, so it appears only
where your organisation has that module switched on. Above that gate, your role
decides what you can do:
-
Viewer holds
playbook:read: open the list, filter it, read any detail.New Playbook, the lifecycle buttons, the step controls and the AI drafting button are not rendered. -
Contributor adds
playbook:create, soNew Playbookappears, and the create form takes a first list of steps. Once the playbook exists, a Contributor reads it but cannot change its steps or status, and does not see the drafting button — that writes steps onto the record, which needs update rights. -
Manager and
Admin also hold
playbook:updateandplaybook:execute. In the detail they see the lifecycle buttons (Activate,Cancel Playbook,Reopen,Delete Playbook), a status dropdown on every step, the add-step field, the remove-step control and the AI drafting button.
The screenshot below was captured as a Contributor; roles are set out in Roles at a glance.
What's on this screen
Playbooks lives at /playbooks. The page opens with the heading
Playbooks, the line “Create and manage incident response playbooks
with automated steps.”, and a New Playbook button at the top right.
One filter sits below it, the All Statuses dropdown; this table has
no free-text search of its own, and the Search… box in the
application bar covers the whole application rather than these rows.
The table has four columns and no actions column: Playbook (the
title, with a one-line description beneath where one is set, cut off with an
ellipsis when it runs long), Status (a coloured chip),
Progress (a bar and its percentage) and Last Updated.
The whole row is the control — selecting anywhere on it opens the detail.
Beneath the rows sit a “Showing … of …” count and Previous /
page-number / Next controls; twenty rows load at a time. The
captured screen shows a well-used list: playbooks at every status —
Active runs part-way through, some Completed at 100%,
new ones at Draft and 0%, and a Cancelled one that
stopped at 20%.
-
Select the
AIgroup in the navigation rail. It expands to showPlaybooks, alongsideAI DashboardandAI Agentswhere the AI assist module is also on; choosePlaybooksto load this list. -
The open-book icon in the application bar opens the in-app User Guide at the
chapter for the screen you are on — this chapter, from here. (The
?icon beside it opens the separate help panel.) -
Your name, just before
Sign outat the right of the application bar, shows which account, and so which role, you are working as. That decides whether the button below is rendered at all, and which controls the detail offers. New Playbookopens the create dialog described below.
Narrowing the list
- Open the
All Statusesdropdown above the table. -
Choose
Draft,Active,CompletedorCancelled. The table reloads from the server with only playbooks in that state, and the “Showing … of …” line and the paging controls update to match. -
Where the chosen status matches nothing, a panel headed “No results found”
replaces the table, with a
Clear filtersbutton that brings the full list back.
Creating a playbook
The form opens the record and, if you already know them, its first steps. Steps can be added or drafted afterwards too.
-
Select
New Playbook. A dialog headedCreate Playbookopens over the list, with aTitlefield, aDescriptionbox, aStepslist holding one empty row, andCancelandCreatein its footer. -
Type a
Title. It is required — the label carries a red asterisk — and takes up to 200 characters. Name it after the situation it answers, so one column identifies it. -
Add a
Description. It is optional, holds up to 1,000 characters, and is read later by the AI drafting action as the playbook's scope — real context here makes the drafted steps markedly more specific. -
Under
Steps, type a step title (up to 200 characters) into theStep Namerow. SelectAdd Stepfor another row, and the bin icon beside a row to remove it. Rows left empty are ignored, so you can leave the list blank and add steps later. This is the only place a Contributor can give a playbook its steps. -
Select
Create. The button readsCreating…while it saves, then a “Playbook created successfully” message appears, the dialog closes and the list refreshes with the new playbook atDraftand0%. Any steps you typed are saved in order, each atNot Started.Cancelsaves nothing. The new record has no assignee; the template key and control link that some playbooks carry are set elsewhere, not on this form.
The field is marked required, so with the title empty your browser blocks the submit and prompts you to fill it in. A title of spaces alone gets past that check and is refused inside the dialog instead, as a red “Title is required” message; either way nothing is saved. Where the save itself fails, a “Failed to create playbook” message appears in that same place and the dialog stays open, so your text survives.
Reading a playbook
-
Select any row. A dialog opens headed with the playbook's title, and the
record loads. A link from an incident's
Response Playbookspanel opens the same dialog directly, at an address of the form/playbooks?playbook=…; closing it leaves you on the plain list. -
At the top sit the status chip and the progress bar with its percentage, and
— for a Manager or Admin — the lifecycle buttons on the right. A
Descriptionblock follows where one was set, thenOverview— the sourceTemplateby its readable name, the number ofSteps, theAssigned Toperson by name or email, and aCompletedtimestamp once finished. Fields with no value are left out rather than shown blank. -
The
Stepsblock lists every step in order — its number, or a tick once complete, then the title, the description, any note recorded while it was worked, and a “Completed …” time on finished steps. For a reader without update rights, a playbook with no steps yet shows noStepsblock at all; a Manager or Admin always sees it, with the add-step field. -
Metadataat the foot gives theCreatedandLast Updatedtimes. Close the dialog to return to the list.
Working the steps
These controls appear in the detail dialog for a Manager or Admin. Each change saves at once, refreshes the detail and the list, and disables the other controls until it has finished.
-
Use the status dropdown at the right of a step to move it between
Not Started,In Progress,CompletedandBlocked. Aegis recalculates the percentage as the share of steps completed, and the playbook's own status follows: the first step moved toIn ProgressorCompletedmakes itActive, and the last step completed makes itCompletedwith a timestamp. -
To add a step, type its title (up to 200 characters) into the
Step Namefield under the list and selectAdd Step. The step joins the end of the sequence atNot Started; the button stays disabled while the field is empty. -
To remove a step, select the bin icon beside it. A confirmation asks “Remove
this step from the playbook?”; confirm with
Remove Step. The remaining steps are renumbered with no gaps.
Where the playbook was started from an incident, completing a step also writes an entry to that incident's timeline, and completing the last step records the playbook as completed there. See Security incidents.
Activating, cancelling, reopening and deleting
The lifecycle buttons sit to the right of the status chip, for a Manager or Admin. Which ones show depends on the playbook's status.
-
Activateappears on aDraftplaybook. It moves the playbook toActive, and a “Playbook updated” message confirms it. -
Cancel Playbookappears on aDraftorActiveplaybook. A confirmation warns “Cancel this playbook? Its steps can no longer be executed until it is reopened.” Once cancelled, the step dropdowns are disabled. -
Reopenappears on aCancelledplaybook and returns it toDraft, so its steps can be worked again. -
Delete Playbookis always present for these roles. A confirmation asks “Are you sure you want to delete this playbook?”; on confirming, a “Playbook deleted” message appears, the dialog closes and the row leaves the list. There is no undo.
Drafting the steps with AI
The drafting button sits in the detail dialog above the Steps block
and reads Draft steps with AI — or
Re-draft steps with AI where steps exist. It is rendered only for
roles holding both playbook:update and the right to run AI actions
(ai:execute) — in practice a Manager or Admin.
-
Select
Draft steps with AI. A second dialog opens over the detail, headedDraft response steps with AIand subtitled with the playbook's title. It states that Aegis will draft a detect → contain → eradicate → recover → lessons-learned sequence from the playbook's scope and its linked control. - Where the playbook already holds steps, an amber warning appears here. Applying a draft writes the whole sequence, so it replaces rather than merges — any step it does not reproduce, and any note or progress held against that step, goes with it. On a playbook already being worked, re-draft only when you mean to start again.
-
Select
Draft with AI. The dialog switches to a progress view listing three stages — reading the scope, structuring the phases, drafting the steps. Every way of closing it is disabled while it runs, because a draft in flight cannot be stopped. -
The drafted steps arrive as an editable list — each a number, a title field
(up to 200 characters), a description box and a
✕to drop it. Reword and delete freely; nothing has been written to the playbook yet. -
Select
Apply & save. Any step whose title you emptied is dropped, the rest are renumbered from 1 and saved, a “Playbook steps saved.” message appears and the detail refreshes with the newStepsblock and a recalculated percentage.Draft againdiscards the draft; empty every title and the save is refused with “Keep at least one step before saving.”
The AI assist
The action reads the playbook's title, description and linked framework control,
and returns a step list grounded in that context and in general
incident-handling duties under laws such as NIS2 (a European cybersecurity law)
and DORA (the EU's financial-sector digital resilience regulation). It proposes;
you decide. The steps reach the record only on
Apply & save, and the action never sets a playbook's status
directly. A drafted sequence is a starting point, never an authority — review it
against your own obligations before relying on it during an incident.
The ordinary AI gating applies: the AI assist feature must be on your
organisation's licence, the first use asks you to acknowledge an AI-transparency
notice (an EU AI Act obligation), each run counts against the monthly allowance,
and runs are rate-limited per user. Where AI is not configured or the allowance
is spent, the dialog reports “AI could not draft the steps.” with the reason
beneath, and offers Retry and Close. Usage is reported
on the AI Dashboard.
Playbook statuses
| Stored value | Chip | What it means |
|---|---|---|
DRAFT |
Draft, grey |
Being prepared; work has not started. Every new playbook starts
here, and
Reopen returns a cancelled one here.
|
ACTIVE |
Active, blue |
Being worked — set by Activate, or automatically once a
step is In Progress or Completed. A step
left at Blocked alone does not move the playbook here.
|
COMPLETED |
Completed, green |
Every step is done; set automatically when the last step is
completed, and the detail shows a Completed timestamp.
|
CANCELLED |
Cancelled, red |
Abandoned before completion through Cancel Playbook.
Steps cannot be worked until it is reopened; the progress reached is
kept.
|
Statuses are stored in upper case but shown as ordinary words in the chips and the filter.
Tips and limits
-
A workspace with no playbooks shows a panel headed “Nothing here yet” with
the line “No items have been created yet.” It carries no button — not even
for a
Contributor — so start
from
New Playbookin the page header. -
There is no edit form. A playbook's title, description and assignee cannot
be changed on either screen today, and step titles cannot be edited in place
— remove the step and add it again, or re-draft with AI. Renaming,
reassigning and step notes are playbook API operations at present, needing
playbook:update(step notes:playbook:execute). -
The create dialog on this page offers no template picker. Aegis ships five
templates — access control remediation, patch management, incident response,
data protection and vendor assessment — and they are used from an incident:
its
Response Playbookspanel has aStart playbookcontrol that builds a playbook from the chosen template, steps included. See Security incidents. - A background routine can run a whole sequence, but nothing in the interface starts it; playbooks on this screen move forward as people set their step statuses.
- Status is the only filter here, and there is no per-column sort. Name playbooks so the title alone identifies them.
Where this connects
Playbooks are the response side of Security incidents, where a playbook can be started from a template and its step progress shows on the incident's timeline; the end-to-end story is told in Scenario: a security incident. Rules that open an incident unattended are covered in Automatic incident rules, and triggered automation in Workflows. For standing authored instructions with an approval lifecycle, use Procedures; the control a playbook remediates is described in Control mapping.