> 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/creating-new-objects.md). # Creating New Documentation The **Create** function allows you to build and organize new documentation in your Library, ensuring your content remains structured and easy to navigate. *** ## Comparing EPC & IMS Hierarchies In IMS, documentation is stored in the [**Library**](/interfacing-help-files/drafts/searching-for-objects-in-the-library/accessing-and-navigating-the-library.md), beginning with **modules** or **roots.** Under each root, you can create folders and subfolders, which contain the individual documentation: * **Root** → **Folder** → **Subfolder(s)** → **Documentation** {% hint style="info" %} A **root** is the top-level category for a specific type of documentation, such as **Process**, **Risk**, or **Document***.* {% endhint %} In EPC, documentation is organized differently. Each **module** contains **sets**, followed by folders and subfolders leading down to individual documentation: * **Set** → **Folder** → **Subfolder(s)** → **Documentation**
{% hint style="success" %} To ensure your hierarchy translates correctly from EPC to IMS, follow these simple rules: * To create a **first-level folder** in IMS, create a **Set** in EPC. * To create a **second-level folder or deeper** in IMS, create a **Folder** in EPC. {% endhint %} *** ## How to Create Documentation In **Phase 1**, the **Create** function is not yet available in the platform. All creation actions must be performed in EPC. For instructions on creating documentation in EPC, refer to the following topics: * [Create Documentation with AI](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/object-generation) * [Parse Process Images or Videos & Regulatory Files with AI](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/13-5-ai-content-parsing-in-epc) * [Create Sets](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-2-1-create-sets) *(first-level folders in IMS)* * [Create Folders](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-2-2-create-folders) (*second-level folders or deeper in IMS)* * [Create Objects ](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-2-3-create-objects) (*documentation in IMS)* *** ## See Also
Cover image
Viewing Documentation in the Library

Browse your documentation directly in the New Experience.		library icon.pngViewing Documentation
Switching Between EPC and the New Experience

Switch to EPC to create and manage documentation.		IMS Icons (3).pngSwitching Between EPC and the New Experience
--- # 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/creating-new-objects.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.