> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/templates.md). # Templates You write the same two things over and over in Zero: meeting notes and outreach emails. Templates let you agree on their shape once, so notes across the team stay comparable and nobody rewrites the same email from scratch. Define them in settings, then type `/` wherever you are writing. They come in two groups. **Meeting notes** templates appear in every note editor — record notes, meeting notes on calendar events, standalone notes. **Emails** templates appear in the email composer, the bulk composer and the LinkedIn message composer. ## Managing templates **Settings → Workspace → Templates**, admins only.
Templates settings with empty Meeting notes and Emails sections, each offering a New template button
### Create a template **New template** next to the **Meeting notes** or **Emails** heading opens an editor for three things: an **Icon and color** so it is recognizable in the picker, a **Template name** (which is what `/` matches against), and the **Content** itself — headings, lists and formatting all survive insertion. **Save** adds it for the workspace. ### Edit or delete a template Click a row to reopen it in **Edit template**. The trash icon, confirmed with **Delete template**, removes it for everyone. ## Using templates ### Insert with `/` Type `/` while writing to open the insert menu. Templates are in the **Snippets** group; keep typing to filter by name, and selecting one drops its content at the cursor. ### Start a note from a template An empty note shows a **Templates** section listing your meeting note templates. Clicking one fills the note — quicker than the `/` menu when you are starting from nothing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zero.inc/settings/templates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.