> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/contributors/toolkits/toolkits/standards/define-custom-fields-for-standard-output-document-headers.md).

# Define custom fields for standard output document headers

Global admins can modify the content fields of Document module on *admin/utilities/tenants/edit* screen in *Collections* section for a specific tenant if needed. The *Standards/Document/Content* collection of Global tenant contains the default fields used when a new tenant is created:

<figure><img src="/files/ykIgO6whciHftx0tnd25" alt="Define custom fields 01"><figcaption></figcaption></figure>

Global admins can override the default items for each tenant. Open the Collections panel in the tenant you want to edit and define new collections.

<figure><img src="/files/4jJim2xP8VvmiavqdGnO" alt="Define custom fields 02"><figcaption></figcaption></figure>

Go to the Utilities/Labels table and add labels for your new fields:

<figure><img src="/files/SrZ6MNFew6SYuTOOziVj" alt="Define custom fields 03"><figcaption></figcaption></figure>


---

# 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://docs.shiftiq.com/contributors/toolkits/toolkits/standards/define-custom-fields-for-standard-output-document-headers.md?ask=<question>&goal=<endgoal>
```

`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.