> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/user/envelope-processing-flow-template-configuration/metadata-in-envelopes.md).

# Metadata in Envelopes

This document explains how to show envelope metadata in envelopes created from a template.

### Turn on metadata display

{% columns %}
{% column %}

1. Open the template in edit mode.
2. Open **Template settings**.
3. Open **Envelope properties**.
4. Enable **Show metadata**.
5. Click **Save**.
   {% endcolumn %}

{% column %}

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2Fb3wonMpIoHTe6B7DNyJ8%2Fimage.png?alt=media&amp;token=17331651-3944-48ab-b9c4-c7c53ab07ff6" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Result

DocStudio shows the metadata block in envelopes created from this template, but only if the envelope contains metadata values. If there is no metadata, the block stays hidden.

### Related topics

* [How to Create and Configure a Template](https://support.docstudio.com/user/template-builder/template/how-to-create-and-configure-a-template.md)
* [How to Manage Template Settings](https://support.docstudio.com/user/template-builder/template/how-to-manage-template-settings.md)
* [Envelope Processing Flow Overview](https://support.docstudio.com/user/envelope-processing-flow-template-configuration/envelope-processing-flow-overview.md)


---

# 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://support.docstudio.com/user/envelope-processing-flow-template-configuration/metadata-in-envelopes.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.
