> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/templates/create-and-edit-templates.md). # Create and edit templates Build a reusable request once, then send it again and again without rebuilding the checklist. A template is a saved request without recipients: the checklist, attachments, forms, reminders, expiration, tags, subject, message and sending options. Each time you send from it, Pipefile copies the template into a new request. Editing a template later never changes requests you've already sent. Templates are available on every plan. ## Open the template manager Click the arrow next to **New Request** in the left sidebar. The **Create from Template** menu lists your templates. Click the gear icon (**Open Template Manager**) to open **Manage Templates**, where you create, edit and organize them. ## Create a template There are three ways to start. {% stepper %} {% step %} ### Start a new template In **Manage Templates**, click the plus icon (**New Template**), or go to `https://pipefile.com/dashboard/request/template/new`. The page is titled **Create New Template**. {% endstep %} {% step %} ### Name it and build the request Enter a **Template Name**. Then set up the request the same way you would a new one: * **Recipient Roles**: the roles recipients fill, used when the template includes forms to sign. See [E-signature](/forms-and-esignature/e-signature.md). * **Reminders**: choose how often to **Send** reminders (**Never** to **Every 14 Days**; the default is every 3 days). * **Days To Expire**: how many days each request stays open, from 1 to 365 (the default is 30). The expiration date is set from this number on the day you send. * **Tags (Optional)**: tags copied onto every request sent from the template. * **Checklist** or **Open-Ended**, with items, sections, instructions, attachments and fillable forms. See [Build your checklist](/requests/checklists-and-sections.md) and [Fillable forms](/forms-and-esignature/fillable-forms.md). {% endstep %} {% step %} ### Add the sending options Click **Next**. In the **Create Template** dialog, enter the **Subject** and an optional **Message**, and pick a cloud folder if you want uploads exported automatically (see [Cloud storage integrations and auto-export](/reviewing-and-exporting/cloud-storage-and-auto-export.md)). Click **Advanced** to set the **Language** recipients see and a **Notification Sequence** (see [Reminders and notification sequences](/reminders-and-notifications/reminder-sequences.md)). {% endstep %} {% step %} ### Save Click **Create Template**. The **Template Saved** dialog lets you share the template with your team right away, or close it and share later. See [Share, lock, reorder and duplicate templates](/templates/share-lock-reorder-and-duplicate.md). {% endstep %} {% endstepper %} ### Save a request you've already built * **While composing a request:** click **Next**, then **Save as Template** below the **Send Request** button. Name it and click **Create Template**. Your draft stays open so you can still send it. * **From a request you've sent:** open the request, open the **...** menu and choose **Save as template**. Enter a **Template Name** and click **Save as Template**. ## Edit a template In **Manage Templates**, click the pencil icon (**Edit**) next to a template, or choose **Edit Template** from its **More Options** menu. The **Edit Template** page has the same fields as the create page. Click **Next**, then **Save template**. If you leave the page with unsaved changes, Pipefile asks before discarding them. You can also describe changes in plain language and let the [AI Assistant](/ai-assistant.md) propose them for an existing template. You review each change before it's applied. {% hint style="info" %} A locked template can only be edited by its owner and team admins. Teammates see a lock icon instead of the edit controls. See [Share, lock, reorder and duplicate templates](/templates/share-lock-reorder-and-duplicate.md). {% endhint %} ## Delete a template In **Manage Templates**, click the trash icon (**Delete Template**). Type `DELETE` to confirm and click **Delete Template**. * Requests already sent from the template are not affected. * Any [lead forms](/intake/lead-forms.md) that use the template are deleted with it. The dialog tells you how many. * A deleted template can't be restored. ## Related * [Send from a template](/templates/send-from-a-template.md) * [Publish and import templates](/templates/publish-and-import-templates.md) --- # 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://support.pipefile.com/templates/create-and-edit-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.