> For the complete documentation index, see [llms.txt](https://docs.subscripta.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subscripta.app/builder/signature-fields-reference.md).

# Signature fields reference

These are the main fields available in the Builder.

## Identity

* **Full name**: required.
* **Email**: required and used for mail links.
* **Job title**: role or position.
* **Department**: can be selected from saved departments.
* **Company name**: company or brand name.

## Contact

* **Phone**: used for phone links.
* **Website**: used for website links.
* **Social links**: supported platforms appear as icons in templates that include social rows.

## Branding

* **Primary color**: main brand color.
* **Accent color**: secondary brand color.
* **Font**: email-safe or supported web font depending on the design.
* **Template**: layout used to render the signature.

## Media

* **Profile photo**: employee avatar or headshot.
* **Company logo**: brand logo.
* **Campaign banner**: promotional image shown in the signature.
* **Banner click URL**: optional tracked destination for the banner.

## QR Code

* **Show QR**: displays a scannable vCard QR code.
* **QR link URL**: Business feature that can make the QR image clickable.


---

# 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.subscripta.app/builder/signature-fields-reference.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.