Snippets allow you to create reusable blocks of procedure content that can be inserted into other procedures. They help reduce duplication, improve consistency, and make it easier to maintain standardized workflows over time.
Snippets support three types: Content, Step, and Section. Each type defines the level of structure the snippet contains and how it behaves when used in a procedure.
All snippets are managed centrally from the Library module and can be reused across multiple procedures.
Snippets Library
All snippets, regardless of type, are accessed from the Library module in the left navigation.
The Snippets Library can be filtered by Tags.
When filters are applied, the Views can be saved either for yourself only or sharable with the team.
Save Views
Users can save search terms, filters, and custom column settings as Saved Views .
Access and switch between views from the new dropdown in the top-left corner.
Click + Save View in the drop down to save a new view of the current settings.
Check the "Publish to Team" box to make the saved view available to others.
You must be a workspace Editor or Admin to publish a Saved View. Other users can view or apply the saved views, however only the original creator is able to make changes to the view.
Hover over an existing view and use the pencil and trash can icons to edit or delete the view.
Create a new snippet:
Navigate to Library > Snippets
Click + New Snippet
Enter a name and optional description
By default, new snippets are created as Content snippets.
Snippet Types
Snippets fall into one of three types. The snippet type determines what the snippet contains and how it behaves when inserted into a procedure.
Content Snippets
Content snippets are the most lightweight and flexible snippet type. They contain only one content block but are not necessarily a full procedure step.
Content snippets are designed to be inserted inside steps and are ideal for reusable instructions, warnings, notes, or reference material that should not require a separate step or signoff.
Key Characteristics:
Default snippet type when creating a new snippet
Can be inserted directly into steps
Do not require signoff
Do not have step-level settings
This allows teams to reuse structured content without forcing every reusable element to be a step or section.
NOTE:
Content snippets can only be one content block. Adding more than one content block will automatically convert to a Step Snippet.
Field Input references, conditionals, dependencies, and Builds content blocks are not supported.
Due to the flexibility of content snippets, the individual content snippets can be added to a step which contains conditionals or dependencies.
Step Snippet
Step snippets represent a complete procedural step that can be reused across procedures.
When a snippet is a step:
A Step Name field is required
Contains one or more content block
Signoff configuration becomes available
Step-level settings can be applied
Step snippets behave the same as steps created directly inside a procedure and can include content blocks, inputs, attachments, and other step details.
NOTE:
Step snippets can only contain one step. Adding more than one step will automatically convert to a Section Snippet.
Field Input references, conditionals, dependencies, and Builds content blocks are not supported.
Section Snippets
Section snippets allow you to reuse an entire section of a procedure, including multiple steps and their configuration.
When a snippet is a section:
A Section Name field is required
The snippet can contain multiple steps
Each step retains its own content, signoffs, and settings
Section snippets are ideal for standardized process phases, repeated checklists, or complex procedural segments that appear in multiple procedures.
Snippet Type Conversion Rules
Snippet types can be elevated, but they cannot be downgraded.
Snippets can ONLY be converted during creation. Once saved, the type can not be changed.
Supported conversion path:
Content → Step → Section
Once a snippet is converted to a higher type, it cannot be converted back to a lower type. This prevents structural inconsistencies when snippets are reused across multiple procedures.
Converting Content Snippets to Steps
A content snippet can be converted into a step snippet in two ways:
Adding more than one content block automatically converts the snippet to a Step snippet
Clicking Convert to Step manually converts a single-content-block snippet into a step
Once converted, the snippet gains step-level configuration options and cannot be reverted back to a content snippet.
Converting Step Snippets to Sections
A step snippet can be converted into a section snippet in two ways:
Adding more than one step automatically converts the snippet to a Section snippet
Clicking Convert to Section manually converts the snippet
Once converted, the snippet becomes a section and cannot be reverted to a step.
View, Edit, Duplicate, Delete Snippets
From the Snippets Library, click into a Snippet name to view, edit, or delete a snippet.
Click the blue Edit button to edit, or use the 3 dot menu in the top right corner to Duplicate Snippet or Delete Snippet.
Snippet Details such as Type, Created by / date, and Last Edited by / date are displayed in the Details panel on the left side.
The Where Used section on the left displays the procedures where the snippet is currently being used as well as links to the procedures.
Tags for the Snippet are also configured from this screen.
Once any changes are made, but sure to save them by pressing the save icon in the top right corner.
The changes will not propagate to procedures automatically as that would unintentionally bypass the review and release process.
To apply the new Snippet changes, navigate to the procedures in the Where Used section, navigate to the Step or Section containing the snippet in the draft edit, and choose whether to Accept Changes or Detach.
Detaching the Snippet will remove it from the Where Used list and prevent any future snippet updates from propagating.
Creating Snippets from Within a Procedure
Snippets can be created directly from a procedure draft while in Edit mode.
Only Step or Section snippets can be created from within a procedure.
Content snippets must be created from Library > Snippets.
Save a Step or Section as a Snippet
Open the procedure in Edit mode
Hover over the Step or Section you want to reuse
Click the + icon to the left of the Step or Section name
Select Save as Snippet
A Save As Snippet window will appear.
Enter:
Name (required)
Description (optional)
Click Submit to save.
The new snippet will be available under Library > Snippets and can be reused in other procedures.
Snippets are visible to all users in the current workspace.
Inserting Snippets into a Procedure Draft
Snippets can be inserted into a procedure while in Edit mode.
Insert a Content, Step or Section Snippet
Open the procedure in Edit mode
Click the + icon next to a Section, Step, or content block
Select Insert Snippet
Choose the snippet from the list
Click Insert Snippet
The selected snippet will be inserted directly below the selected Section, Step, or Content Block.
Section snippets insert full sections
Step snippets insert complete steps
Content snippets can be inserted inside steps using the content block editor
Detaching a Snippet
When a snippet is inserted into a procedure, it remains linked to the original snippet.
If you want to modify the snippet in a specific procedure without affecting the original:
Hover over the inserted snippet
Select Detach
Confirm by clicking Proceed
Detaching breaks the link to the original snippet and allows you to freely edit that version without impacting other procedures.
Snippet Updates in Procedures
If a snippet has been modified, entering Edit mode in a procedure that contains that snippet will notify you of the change.
You will have the option to:
Accept the latest version of the snippet
Retain the existing version and detach it
Use the toggle to switch between the Procedure Version of the snippet and the Latest version to easily see the changes that have been made.
This ensures you maintain control over updates while preserving consistency across procedures.