> 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/4-publishing-visualizations/4.2-watermarks-for-pdf-publishing-tasks.md).

# 4.2 Watermarks for PDF publishing tasks

For following PDF publication jobs is possible to set a watermark:

* AutoCAD PDF
* Inventor PDF
* Office PDF

Setting: Entity – Job – Custom Processes - Watermark

![](https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2F0nbtNLuGpSFKmNMseGKf%2Fimage.png?alt=media\&token=76b41aa9-1de4-49ff-ad07-56408a6a2dc9)

![](https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2FFsGIgmHH8xphO0Ssd6Jf%2Fimage.png?alt=media\&token=b7c07c78-43ec-43be-8d1f-c9934de7025e)

1. The watermark configuration activation
2. Select the watermark type Text/Image 
3. Watermark text setting 
   1. Free text 
   2. Numbering scheme 
   3. Vault property 
4. Font and size selection (for A3 full-page watermark, the font size is about 90) 
5. Font color select 
6. Watermark position 
7. Specific drawing format creation

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

• If there are images on the page, they will overlay the watermark (images are not                           transparent)&#x20;

• If the text is formatted with a background (text highlight color), the watermark will be overlaid.&#x20;

This is the same behavior as if a watermark was selected directly in a word.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.besmart.software/p4v/publisher4vlt-description/4-publishing-visualizations/4.2-watermarks-for-pdf-publishing-tasks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.