> 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/publish-and-import-templates.md).

# Publish and import templates

Publish a template as a link other Pipefile users can import into their own account.

Publishing turns a template into a link you can give to Pipefile users outside your team, such as colleagues in your industry. Anyone with the link who has a Pipefile account can import their own copy. Sharing with your own team works differently; see [Share, lock, reorder and duplicate templates](/templates/share-lock-reorder-and-duplicate.md).

## Publish a template

Only the template's owner or a team admin can publish it.

{% stepper %}
{% step %}

### Open the publish options

Click the arrow next to **New Request**, then the gear icon (**Open Template Manager**). On the template, open **More Options** and choose **Publish To Web**.
{% endstep %}

{% step %}

### Turn on Publish to web

Turn on the **Publish to web** switch (**Anyone with the link can view**). It takes effect immediately.
{% endstep %}

{% step %}

### Copy the link

Copy the link that appears below the switch. It looks like `https://pipefile.com/template/<template-id>`. Send it to whoever you want to have the template.
{% endstep %}
{% endstepper %}

To unpublish, open **Publish To Web** again and turn the switch off. The link stops working for new imports. Copies people already imported are theirs and are not affected.

{% hint style="warning" %}
Anyone who has the link and a Pipefile account can import the template's contents, including its checklist instructions and any attached files. Don't publish templates that contain client information.
{% endhint %}

## Import a template someone published

{% stepper %}
{% step %}

### Open the link

Open the template link you were given. If you aren't logged in, Pipefile asks you to log in or create an account first.
{% endstep %}

{% step %}

### Import

The page shows the template's name and who published it, and asks **Would you like to import this template?** Click **Import Template**.
{% endstep %}

{% step %}

### Send or keep it

Pipefile adds the template to your account and opens a new request from it, ready for recipients. You don't have to send it now; the template stays in your **Create from Template** menu and **Manage Templates**.
{% endstep %}
{% endstepper %}

## What an imported copy includes

The copy belongs to you. Editing it doesn't affect the original, and the publisher's later edits don't reach your copy.

| Included                                    | Not included                          |
| ------------------------------------------- | ------------------------------------- |
| Checklist, sections, items and instructions | The publisher's notification sequence |
| Attached files and fillable forms           | The publisher's cloud export folder   |
| Subject, message and language               | Sharing, group and lock settings      |
| Reminder frequency and days to expire       |                                       |
| Tags and recipient roles                    |                                       |

After importing, review the copy and set your own sending options, notification sequence and export folder. See [Create and edit templates](/templates/create-and-edit-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/publish-and-import-templates.md?ask=<question>&goal=<user_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.