> For the complete documentation index, see [llms.txt](https://help.holixa.com/holixa-publisher4vlt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.holixa.com/holixa-publisher4vlt/fundamentals/2-add-in-configuration/2.4-add-edit-and-delete-publication-settings/2.4.3-publishing-out-from-vault.md).
# 2.4.3 Publishing Out From Vault
When setting up Publishing Out From Vault, the publication will be run to the local or shared disk. Set the main directory where the published files are to be saved. The path can be specified in classic (D:\PublishFiles) or UNC format (\server01\PublishFiles).
{% hint style="info" %} **NOTE**
The path may not exist during the configuration – Publisher4VLT create the path during the publication. However, it is necessary that write and change rights are set in the path for the user under which the publication is running (the user under which the Job Processor is running). For a better orientation in published files, it is possible to use one of the pre-prepared schemes for dividing published files into folder. The path will be then in the form Main folder\Publication scheme
{% 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://help.holixa.com/holixa-publisher4vlt/fundamentals/2-add-in-configuration/2.4-add-edit-and-delete-publication-settings/2.4.3-publishing-out-from-vault.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.