> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/message/email/templates-and-modules-management/how-to-synchronize-a-module-across-your-orchestrations.md).
# How to synchronize a module across your orchestrations?
When several email messages share the same header, footer, or legal block, save it once as a synchronized module and update it from a single place.
{% hint style="info" %}
Synchronized modules are available on request for certain customer tiers. Reach out to your Customer Success Manager to learn more.
{% endhint %}
## Synchronizing a module
Save your module as explained in [How to save modules on the email composer?](file:///Applications/Markdown%20Editor.app/Contents/Resources/how-to-save-modules-on-the-email-composer.md), choose **Project** in the **Folder** field, then turn on synchronization in the module settings:
Every message or template into which you drag this module stays linked to the version stored in your project library. Update the module once, and the changes reach every campaign and automation using it.
## Editing a synchronized module
If you edit a synchronized module directly in a message, the link with your library is put on hold until you decide what to do with your changes:
* **Save changes to the module**: your edit is applied to the library and to all the messages using the module.
* **Revert changes**: the module goes back to its library version.
* **Unlink and apply changes locally**: your edit stays in this message only, and future updates of the module will not reach it.
Users with **text-only access** can edit text inside a synchronized module. Because they cannot trigger “Save changes to the module,” their edit never affects the module stored in the library. No “Changes detected” status is raised: the module’s link to the library stays marked as in sync.
{% hint style="info" %}
Anyone who can edit a message or template can update a synchronized module for everyone. This includes messages used in automations. Keep synchronization for the elements owned by a single team: header, footer, legal mentions.
{% endhint %}
---
# 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, and the optional `goal` query parameter:
```
GET https://doc.batch.com/guides-and-best-practices/message/email/templates-and-modules-management/how-to-synchronize-a-module-across-your-orchestrations.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.