> For the complete documentation index, see [llms.txt](https://docs.soraco.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soraco.co/docs/faq/how-to-prevent-the-qlm-management-console-from-overwriting-local-email-templates.md).

# How to prevent the QLM Management Console from overwriting local email templates

Email templates are initially stored locally on your system and automatically uploaded to the server when the Email Templates Editor is closed.

When you launch the Email Templates Editor, the templates are automatically downloaded from the server. When the templates are downloaded, any local email template that is more recent than the server version is not overwritten.

To force QLM to overwrite local email templates, do the following:

* Locate the Email Templates folder. To locate this folder:
  * Go to the Manage Keys tab
  * Click Sites
  * Go to the Files and Folders tab
  * Copy the Email Templates folder and paste it in Windows Explorer to go to that folder
* In that folder, create an empty file called serverNoOverwrite.xml.

The serverOverwrite.xml will be automatically deleted the first time it is found so this technique is a one-time method.

Note that the file will be overwritten if a local email template is older than its server equivalent.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.soraco.co/docs/faq/how-to-prevent-the-qlm-management-console-from-overwriting-local-email-templates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.