> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/monolith-features/settings/editor-templates.md).

# Editor Templates

Editor Templates are reusable note templates for Monolith’s note-taking system.

Teams can use editor templates to standardize how notes are written for common workflows, collection procedures, examinations, reviews, or other repeatable processes. Templates can be kept private for your own use or shared with other Monolith users in your organization.

### When to Use Editor Templates

Use editor templates when your team regularly documents the same type of information in notes.

Common examples include:

* Evidence intake notes
* Device collection notes
* Phone examination notes
* Computer examination notes
* Processing request notes
* Review or quality assurance notes
* Internal lab process notes
* Customer-specific documentation formats

Editor templates are especially helpful when a process requires information that is not already captured in Monolith’s standard case, evidence, acquisition, storage, or reporting fields.

### Access Editor Templates

To manage editor templates:

1. Open **Settings** from the left navigation.
2. Select **Editor Templates**.
3. Review the existing templates or create a new one.

The Editor Templates page shows available templates, when they were created, whether they are shared, and actions to edit or delete each template.

### Create an Editor Template

To create a new editor template:

1. Open **Settings**.
2. Select **Editor Templates**.
3. Click **New Template**.
4. Choose whether to enable **Share With Others**.
5. Enter a **Template Name**.
6. Add the template content.
7. Click **Save**.

The template content editor supports common formatting options such as headings, bold text, italic text, underlined text, strikethrough text, bulleted lists, numbered lists, and text alignment.

### Shared Templates

Editor templates can be private or shared.

If **Share With Others** is enabled, other Monolith users in your organization can use the template when creating notes.

If **Share With Others** is not enabled, the template is only available to the user who created it.

{% hint style="info" %}
Shared templates are useful for team-wide processes where notes should follow a consistent format across users.
{% endhint %}

### Create a Template From an Existing Note

Editor templates can also be created from notes already written inside a case.

If you create a note that would be useful to reuse later, save that note content as a template from within the note editor. After it has been saved as a template, you can return to **Settings > Editor Templates** to manage, edit, share, or delete it.

This is useful when a strong note format develops naturally during casework and should be reused for future cases.

### Edit an Editor Template

To edit an existing template:

1. Open **Settings**.
2. Select **Editor Templates**.
3. Find the template you want to update.
4. Click **Edit**.
5. Make the necessary changes.
6. Click **Save**.

Changes to a template affect future use of that template. Existing notes that were previously created from the template are not automatically changed.

### Delete an Editor Template

To delete a template:

1. Open **Settings**.
2. Select **Editor Templates**.
3. Find the template you want to remove.
4. Click **Delete**.
5. Confirm the deletion if prompted.

Deleting an editor template removes it from the list of available templates. It does not delete notes that were already created using that template.

### Editor Templates vs. Document Templates

Editor templates are used for Monolith notes.

They are different from document templates, report templates, or other template types that may be used elsewhere in Monolith. Use editor templates when you want to standardize note content. Use document or report templates when you are configuring generated documents or report outputs.

### Best Practices

* Use clear template names that describe the workflow or note type.
* Keep templates structured but flexible enough for real casework.
* Use headings to separate major sections.
* Add prompts or placeholders for information users should remember to document.
* Share templates that should be used consistently across the team.
* Review shared templates periodically to make sure they still match your team’s process.