# Templates

Templates allow you to standardize launch processes by predefining stages, milestones, participants, and required documentation. This ensures consistency and saves time when creating similar launches.

## View templates

View all workspace templates in Settings > Templates with options to:

* **Edit**: click hamburger menu next to template name > Edit (template owner only)
* **Copy**: duplicate existing templates to create variations (template owner only)
* **Create new**: click "Create new template" button (Admins and Makers)

## Create a new template

1. Click "**Create new template**" button
2. **Template basics:**
   * Template name (required)
   * Short description with talking points for users (e.g., "What problem are you solving?", "What users are impacted?", "What are the KPIs?") (required)
3. **Template configuration:**
   * **Add labels:** categorize your template for easy identification
   * **Define stages and milestones**: outline the project workflow
   * **Add participants**: could be teams and/or individuals
   * **Set milestone owners/approvers**: assign teams or individuals to milestones
   * **Required resources:** specify documents needed (e.g., Figma mocks, PRD)
4. Save the template

{% hint style="warning" %}
To add stages to your template, ensure they are created in **Stage Management** first.
{% endhint %}

### Adding teams as participants

* Teams can be assigned as default launch participants
* When assigning milestone owners/approvers, all members of assigned teams become available as individual options

## Use templates

During launch creation, select a template to automatically apply:

* Predefined stages and milestones
* Default participants and team assignments
* Required document placeholders
* Standard milestone owners/approvers

Launches created from templates can be modified:

* **Can modify**: labels, milestones, participants, documentation, milestone assignments
* **Cannot modify:** stage sequence (locked to template structure)

## Update a template

When you update a template:

* Changes only apply to future launches using the template
* Existing launches created from the template remain unchanged
* No retroactive updates to previous launches