> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-in-the-library/merging-documentation.md).

# Merging Documentation

The **Merge** function allows you to combine two documentation objects of the same type into a single object. This is especially useful when duplicates exist, during restructuring, or when you want one piece of documentation to replace another while preserving all relevant impacts and associations.

***

## How to Merge Documentation

In **Phase 1**, the **Merge** function is not yet available in the platform. All merge actions must be performed in EPC.

For instructions on merging documentation in EPC, refer to the following topics:

* [Merge](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-3-7-merge)
* [Merge from the List View](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-9-8-14-merge-in-list-view)

***

## See Also

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Viewing Documentation in the Library</strong><br><br>Browse your documentation directly in the New Experience.</td><td data-object-fit="cover"><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2Fts4TC2xIhTDFDVIbZ4k0%2FIMS-V16-NAV-Library-Icons-53.png?alt=media&amp;token=6fa39ac3-901f-4cc0-b74d-296bdf9eb602">library icon.png</a></td><td><a href="/interfacing-help-files/drafts/searching-for-objects-in-the-library/library.md">Viewing Documentation</a></td></tr><tr><td><strong>Switching Between EPC and the New Experience</strong><br><br>Switch to EPC to create and manage documentation.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FBzOehRRXH52GoVAsyhxM%2FIMS%20Icons%20(3).png?alt=media&amp;token=3cce5594-cd46-4892-8c64-104c51f4bf52">IMS Icons (3).png</a></td><td><a href="/interfacing-help-files/getting-started/switching-between-epc-and-the-new-experience.md">Switching Between EPC and the New Experience</a></td></tr></tbody></table>


---

# 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://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-in-the-library/merging-documentation.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.
