Source: https://fyno.docs.pageloop.ai/documentation/core-features/templates

# Templates

Templates are a one-stop shop for all your message content that needs to be recorded and stored in a safe place within the Fyno App, that can be used when needed.

Be it static or dynamic templates with variable or replaceable parameters for important details and personalisation of messages, we got you covered, as always!

Templates are stored based on the Channel Type as per the Integrations Section. This is the second and crucial step in the Fyno building blocks to create your perfect notification event flow.

## Getting Started with Templates

From the left navigation panel select Templates to open the section.

Let's run through the Templates Page to have a better understanding of how it works.

On the landing page, to the left, you will find an easy toggle to change your view between a card grid and a list view, for your convenience.

Your option to filter out only the **Live** routes is at the top of the page.

### Create

1. To create a new Template Collection click on the "Create+" button on the right side of the page.
2. In the pop-up that appears, fill in a relevant name for the Template.
3. Select a group. This helps you organize all related templates under a single group for easier management.
4. Select the channel you want to create for this template, which can be any/all of:
   - SMS
   - Email
   - WhatsApp
   - Slack
   - Discord
   - Teams
   - Push
   - In-App
5. Once you're ready, click on "**Submit**".

### Template Collection Cards

On the landing page of the Templates section, you will be able to see all the templates created.

You can also search for templates by entering their names using the search bar at the top of the page.

On each template card, you will see:

- Template Name
- Created time/date.
- The corresponding channels for which templates have been configured within that collection. (Explained more in detail below)
- The "More" (Three dots) menu allows you to:
  - Rename your template
  - Delete your template
  - Promote Test to Live

### How to copy Templates to another workspace

Templates can be copied from one workspace to another workspace that you own.

> [!WARNING]
>
> **Prerequisite:** You must have the **Owner** role in the destination workspace to use this feature.

> [!INFO]
>
> **Note:** Only Fyno Templates (**Templates** → **Fyno**) can be copied. External Templates (**Templates** → **External**) are not supported.

#### Before you copy

Only the template itself is copied. Any external dependencies must be resolved or created in the destination workspace before you can use the copied template.

Before copying, ensure you:

- **Components:** If the template uses reusable components, copy those components first (see [Copying Components](#copying-components) below).

#### Steps to copy templates

1. Open the source workspace containing the template.
2. Go to **Templates** → **Fyno**.
3. Click the three-dot (**⋮**) menu on the template you want to copy.
4. Select **Copy to another workspace**.
5. Select one or more templates to copy (if required).
6. Click **Copy Selected Templates**.
7. Choose which version to copy:
   - If you're copying a **single template** that has both Live and Test versions, choose which version to copy. (If only a Test version exists, the Test version is copied).
   - When copying **multiple templates**, the latest available version (Live or Test) of each template is copied automatically.
8. Select up to five destination workspaces where you have the **Owner** role.
9. Click **Confirm** to start the copy process.

The selected templates will now appear in each destination workspace.

#### Template versioning

The versioning behavior of the copied template depends on whether it already exists in your destination workspace:

### When the template does not exist in the destination workspace

- A new template is created as `v1` (Test).

### When the template already exists

- A new standalone version is created without modifying existing versions.
- For example:
  - **Existing version:** `v1` (Test)
  - **Copied version:** `v2`
- You can then:
  - **Save** to make it `v2` (Test), or
  - Click **Go Live** to promote it to `v2` (Live).

> This prevents existing versions from being overwritten and gives you control over when the copied version becomes active.