> 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-lifecycle/managing-the-publication-of-documentation.md). # Managing the Publication of Documentation Publish documentation for end-users—or unpublish it when it needs to be withdrawn. Publishing is the process of making documentation available to end-users. Once a document is published, it can be viewed, referenced, and used by the intended audience. This ensures that approved content is accessible and usable for those who depend on it for their day-to-day operations. {% hint style="warning" %} Publishing occurs only after all prior governance steps—such as endorsement, approval, and attestation (if configured)—are complete. It is then **manually triggered** by users with the appropriate permissions and authorizations. {% endhint %} It is also possible to **unpublish** documentation, allowing you to withdraw a published version and return it to draft status. This ensures that incorrect, mistakenly published, or temporarily unavailable content is no longer visible to end-users. *** ## How Publish & Unpublish Documentation In **Phase 1**, publication management is not yet available in the platform. All publication actions must be performed in EPC. For detailed instructions on publishing and unpublishing documentation in EPC, refer to the following topics: * [Publish](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-5-8-publish) * [Mass Publish](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-9-8-1-mass-publish) * [Unpublish](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-3-12-6-unpublish) *** ## See Also You can use the platform to stay on top of your documentation lifecycle and ensure every task is completed smoothly. Explore the resources below to get started:
Managing Tasks in To Do

View, organize, and complete documentation lifecycle tasks.		to do icon.pngManaging Your Tasks
Permission & Security Management (Admins Only)

Learn about the permissions and authorizations required to access, edit, and manage documentation.		IMS-V16-NAV-Library-Icons-72.pngPermission & Security Management
--- # 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-lifecycle/managing-the-publication-of-documentation.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.