> For the complete documentation index, see [llms.txt](https://docs.bird.com/taxi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/taxi/projects-mailings-and-versions/parent-versions-and-child-versions/synchronising-content-between-the-parent-version-and-other-versions.md).

# Synchronising content between the Parent version and other versions

When you create a new version, it synchronises content with the Parent version, by default.

You can unsync this content by editing any field in a version that's not the parent. This unsyncs the content for this version. It unsyncs on an element by element basis. For example, if you edit the content for a sub-headline, it will only unsync for the sub-headline.

If you then change the same element in the parent version, the edits won't carry through.

You can also control whether an element in a module is inheriting from the parent version or not by using the sync button

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-79da5d76760649def6ec4e31b1dd2e24bc7b6a03%2FScreenshot%2B2019-10-04%2Bat%2B15.42.37.png?alt=media)

If you sync with the parent version, the content in your version will be replaced by the content from the parent version. If you unsync, it will replace it with the content that was there before.

If the parent version hasn't been edited, you can reset the content back to what was in the Email Design System. 

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-6fa21a595dca5214b8452b715a177bff52ec9b0c%2FScreenshot%2B2019-10-04%2Bat%2B15.29.13.png?alt=media)


---

# 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://docs.bird.com/taxi/projects-mailings-and-versions/parent-versions-and-child-versions/synchronising-content-between-the-parent-version-and-other-versions.md?ask=<question>&goal=<endgoal>
```

`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.