**Source URL:** https://limited.veevavault.dev/medical/mdl/component-types/signaturepage

# Signaturepage

**Class:** `metadata`

Signature pages display the manifested signatures for a Vault document.

Learn about [Signature Pages in Vault Help](https://platform.veevavault.help/en/lr/8975).

| Attribute | Metadata | Description |
| --- | --- | --- |
| `label` | Type: String Max length: 60 | UI-friendly string in the Vault's base language. |
| `active` | Type: Boolean | Indicates whether the component is active. |
| `advanced_mode` | Type: Boolean | If `true`, indicates an advanced signature page template. If `false`, indicates a basic signature page template. |
| `file` | Type: File | Reference to the XFA template file. As of 24R3.2, this attribute is deprecated and replaced by `header_richtext`, `footer_richtext`, and `signature_block_richtext`. You must use MDL to edit XFA templates for signature pages created before 24R3.2. |
| `footer_01` | Type: String Max length: 1500 | Footer line 1. As of 24R3.2, signature page headers are populated from the value of the `header_richtext` attribute unless `schema_version`\= `0` or is blank. |
| `footer_02` | Type: String Max length: 1500 | Footer line 2. As of 24R3.2, signature page headers are populated from the value of the `header_richtext` attribute unless `schema_version`\= `0` or is blank. |
| `footer_richtext` | Type: String Max length: 6000 | The HTML for the signature page footer. |
| `header_01` | Type: String Max length: 1500 | Header line 1. As of 24R3.2, signature page headers are populated from the value of the `header_richtext` attribute unless `schema_version`\= `0` or is blank. |
| `header_02` | Type: String Max length: 1500 | Header line 2. As of 24R3.2, signature page headers are populated from the value of the `header_richtext` attribute unless `schema_version`\= `0` or is blank. |
| `header_richtext` | Type: String Max length: 6000 | The HTML for the signature page header. |
| `location` | Type: Enum Allowed values: start\_\_v; end\_\_v | Specifies whether the signature page appears at the beginning or end of the document. |
| `schema_version` | Type: Number | If blank or set to `0`, Vault populates the signature page with values from legacy attributes `header_01`, `header_02`, `signature_block_01`, `signature_block_02`, `footer_01`, and `footer_02`. If set to `1`, Vault populates the signature page with RichText values. |
| `signature_block_01` | Type: String Max length: 1500 | Signature block 1. As of 24R3.2, signature page headers are populated from the value of the `header_richtext` attribute unless `schema_version`\= `0` or is blank. |
| `signature_block_02` | Type: String Max length: 1500 | Signature block 2. As of 24R3.2, signature page headers are populated from the value of the `header_richtext` attribute unless `schema_version`\= `0` or is blank. |
| `signature_block_richtext` | Type: String Max length: 6000 | The HTML for the signature block. |

### Supported Operations

| Operation | Support |
| --- | --- |
| Create | Yes |
| Recreate | Yes |
| Alter | Yes |
| Drop | Yes |
| Rename | Yes |
| Describe | Yes |
| Generate Recreate | Yes |
| Queryable | Yes |

---

**Previous:** [Sharingrule](/medical/mdl/component-types/sharingrule)  
**Next:** [Tab](/medical/mdl/component-types/tab)