> For the complete documentation index, see [llms.txt](https://help.besmart.software/p4v/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/p4v/publisher4vlt-description/2-add-in-configuration/2.1-setting-on-the-general-tab/2.1.1-logging.md).

# 2.1.1 Logging

Logging level possibilities are explain in the table.

![](/files/KqdEW6y3QpXlvf9ee5UU)

Always set the path of log file to the folder, for which the user, under which the Vault client and Job Processor are running, will have permission to write and change the file.

{% hint style="warning" %} <mark style="color:orange;">**Warning**</mark>&#x20;

At this time, it is not possible to share a single log file location across multiple stations, it means each Vault client and Job Processor with Publisher4VLT add-in installed must have an independent path specified.
{% 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:

```
GET https://help.besmart.software/p4v/publisher4vlt-description/2-add-in-configuration/2.1-setting-on-the-general-tab/2.1.1-logging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
