Skip to main content
Add a runbook type

Find out how to add a runbook type and what each type means

Cutover Documentation Team avatar
Written by Cutover Documentation Team
Updated over a month ago

Making use of runbook types will allow you to tailor your workspace to different use cases or needs. Each runbook type can have different configuration of task types and custom fields applied, allowing you to use an entire workspace in many different ways. It enables you to create runbooks that are tailored to a specific use case which will display visual indicators.

The Workspace Manager role can create new runbook types by accessing the Settings cog at the bottom of the blue left hand panel. Then select Runbook Types.

The Runbook Types screen is displayed. All other runbook types that have been added will be listed. To add a new Runbook type, click the blue plus in the bottom right hand corner.

The New Runbook Type modal window displays.

Give your runbook type a name and a description. The description will appear on the runbook create modal to help workspace runbook creators and folder runbook creators decide which runbook type to use when creating runbooks.

Select your visibility - choose one of the workspaces you have workspace manager permissions on. Next, select an icon and colour. This will be the icon users will see within the workspace and it can help to easily identify the runbook type.

The Approval Flow section is used when you want to create a template workflow. Please see this section here for further information.

Additional settings


There are a number of settings which can appear on the Runbook Type Create modal and Edit panel. These are:

Mark as incident

Incidents are events which occur unexpectedly, so this gives you added flexibility when you apply it to your runbook.

Note: If you select this option, you are unable to deselect any of the other Additional Settings.

Features of this functionality are:

  • Auto start: As an incident isn't typically something thats planned, this runbook will start as soon as it's created and users can create tasks as the event progresses.

    • As a result of this there is also no ability to plan or rehearse an incident.

  • No completion: The runbook will run until its manually closed, even when all tasks complete the runbook will still not be marked complete.

    • As a result of this there are no runbook timings that you might see in traditional runbook types, such as planned/ forecasted end time on tasks or the runbook.

  • Activity feed: A live feed of everything that is happening on the runbook including comments, enabling those running the incident to quickly grasp what is happening in one view.

  • The Incident functionality also is capable of being configured to ServiceNow using Apps functionality.

Dynamic mode

Traditionally, for various reasons, runbooks need to be paused in order to be edited; however in some cases they call for greater flexibility. Features of this mode are:

  • The ability to create new tasks while the runbook is in run.

  • Editing not yet started tasks while the runbook is in run.

  • Ability to create streams.

  • Ability to manage users and teams on the runbook.

Only create from template

Workspace runbook creators and folder runbook creators have the ability to freely create runbooks from scratch however this option enables a more granular level of control where required, such as:

  • Users who have the ability to create runbooks, can only create from runbook templates for this particular runbook type.

  • Those users can no longer create runbooks or duplicate runbooks on the workspace.

  • Users must have at least one runbook created before they should turn this setting on, as they will need to make this a template first. We currently have no way for users to make templates via the user interface but this is planned for a future enhancement.

  • Alternatively, users can create templates from scratch using the Cutover API. For more information, see our Developer Portal.

Disable runbook type

When runbook types are no longer required on a workspace, you can now hide a runbook type from being selected for future use. Notable features in this option include:

  • Hidden from all runbook creation modals and no longer available for selection anywhere in the application.

  • Disabled runbook types are still available for selection in filtering and are available for inclusion in dashboard metrics.

  • As this runbook type would still be needed for data purposes we have allowed the user the option to disable rather than delete the runbook type.

Choose your additional settings and then click Create to add your new runbook type to the Runbook Types list or click Cancel to close the modal window.

Did this answer your question?