Tag properties
Every tag you place on a document has a set of configurable properties that control how it looks, how it behaves during signing, and who can see or interact with it. You configure properties in the properties panel on the right side of the template editor.
Properties are organized into four categories: basic, formatting, advanced, and data labels.
Basic properties
These properties are available on all or nearly all tag types and cover the core signing behavior.
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
isRequired | Boolean | false | When enabled, the recipient must fill in or interact with this tag before they can complete their signing step. Tags marked required display a visual indicator during signing. | All interactive tag types |
isReadOnly | Boolean | false | When enabled, the tag is pre-filled by the sender and the recipient cannot change the value. Use this to display fixed information that the recipient should see but not edit. | Text, Number, Date, Dropdown |
label | String | — | A unique key that identifies this tag in your data. Tags that share the same label value auto-populate from one another — fill in any one of them and all matching tags update. See Data labels. | All tag types |
placeholder | String | — | Hint text shown inside the tag before the recipient enters a value. Disappears when the recipient starts typing. Use this to give examples or formatting guidance. | Text, Number, Date |
tooltip | String | — | Help text shown when the recipient hovers over or focuses the tag during signing. Use this for longer guidance that would not fit in the placeholder. | All tag types |
Required vs. optional
Recipients cannot complete their signing step until every required tag on the document is filled in. Optional tags can be left blank. The tag shows a visual indicator when required.
Read-only tags
A read-only tag lets you display a pre-filled value that the recipient can see but not modify. To use this, enter the value in the tag before sending the agreement. The recipient sees the value in place during signing.
Note: Read-only does not apply to signature or initial tags, which must always be completed interactively by the recipient.
Formatting properties
Formatting properties control the visual appearance of text inside a tag and the tag's own border and background. These properties apply to tag types that display text or have an interactive input area.
Text appearance
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
fontFamily | String | System default | The typeface used to render text inside the tag. Select from the available font options in the properties panel. | Text, Number, Date, Dropdown, Auto-fill (Name, Email, Date, Title, Company), Formula |
fontSize | Number | 12 | Font size in points. Available sizes: 8, 9, 10, 11, 12, 14, 16, 18, 20, 24, 28, 36, 48, 72. | Text, Number, Date, Dropdown, Auto-fill, Formula |
fontColor | String (hex) | #000000 | Color of the text rendered inside the tag. Enter a hex color value or use the color picker. | Text, Number, Date, Dropdown, Auto-fill, Formula |
bold | Boolean | false | Renders text in bold weight. | Text, Number, Date, Dropdown, Auto-fill, Formula |
italic | Boolean | false | Renders text in italic style. | Text, Number, Date, Dropdown, Auto-fill, Formula |
underline | Boolean | false | Renders text with an underline. | Text, Number, Date, Dropdown, Auto-fill, Formula |
Alignment
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
textAlign | left | center | right | left | Horizontal alignment of text within the tag bounding box. | Text, Number, Date, Dropdown, Auto-fill, Formula |
verticalAlign | top | middle | bottom | middle | Vertical alignment of text within the tag bounding box. | Text, Number, Date, Dropdown, Auto-fill, Formula |
Tag appearance
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
backgroundColor | String (hex) | Transparent | Fill color of the tag area. Use this to visually group related tags or highlight important inputs. | Text, Number, Date, Checkbox, Dropdown |
borderColor | String (hex) | Theme default | Color of the tag border. | Text, Number, Date, Checkbox, Dropdown |
Advanced properties
Advanced properties control visibility, shared behavior, template-level restrictions, and form-fill mode organization.
Visibility
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
visibilityScope | ALL_RECIPIENTS | ONLY_ASSIGNED_RECIPIENT | SENDER_ONLY | ALL_RECIPIENTS | Controls which parties can see this tag. See the table below for how each value behaves. | All tag types |
concealValueOnDocument | Boolean | false | Hides the entered value on the final signed document. The value is captured and stored, but appears masked in the downloaded PDF. Use this for sensitive data such as tax identification numbers or passwords. | Text, Number |
Visibility scope values:
| Value | Who sees the tag |
|---|---|
ALL_RECIPIENTS | Every recipient in the agreement sees the tag and its value. This is the default. |
ONLY_ASSIGNED_RECIPIENT | Only the recipient assigned to this tag sees it. Other recipients viewing the document do not see this tag at all. |
SENDER_ONLY | Only the sender sees the tag during preparation. The tag does not appear during any recipient's signing step. Use this for internal notes or sender-filled data not intended for recipients. |
Shared tags
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
shared | Boolean | false | When enabled, the tag is shared across recipients. Any recipient who fills in this tag populates it for all other recipients. Useful for information that any party in the agreement can provide. | Text, Number, Date |
requireInitialOnSharedChange | Boolean | false | When enabled alongside shared, any recipient who modifies a value already entered by another recipient must also provide their initials to confirm the change. | Text, Number, Date |
Template-level control
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
templateLocked | Boolean | false | When enabled, the tag's position and size cannot be moved or resized by a sender who is preparing an agreement from this template. The tag is locked in place as defined in the template. | All tag types |
templateRequired | Boolean | false | When enabled, the tag cannot be removed from an agreement based on this template. Senders can still configure other properties but cannot delete the tag. | All tag types |
Form-fill mode
Form-fill mode presents a structured form to the recipient before they sign. These properties control how tags appear in that form step.
| Property | Type | Default | Description | Supported tag types |
|---|---|---|---|---|
formLabel | String | Same as label | The label shown next to this tag in the form-fill step. Set this when you want a different, more descriptive label in the form than the data key used internally. | Text, Number, Date, Dropdown, Checkbox, Radio |
formGroup | String | — | Groups related tags into a named section in the form-fill step. Tags with the same formGroup value are displayed together under that section heading. For example, "Borrower Information" or "Property Details". | Text, Number, Date, Dropdown, Checkbox, Radio |
formOrder | Integer | — | Controls the display order of tags within their formGroup. Tags with lower numbers appear first. Tags without a formOrder value appear after ordered tags, in the order they were added. | Text, Number, Date, Dropdown, Checkbox, Radio |
Data labels
The label property serves a dual purpose: it is used as a data key for API and merge-field integrations, and it drives auto-population between tags.
Auto-population rule: When two or more tags on the same document share the same label value, filling in one automatically populates the others with the same value. This works in real time during signing — the recipient types in one tag and all matching tags update immediately.
When to use auto-population
Use this when the same piece of information needs to appear in multiple locations. Common examples:
| Scenario | Label to share |
|---|---|
| Recipient name appears in the signature block and at the top of a cover page | full_name |
| Company name appears in the header and in a liability clause | company |
| Effective date appears at the start of the agreement and in a termination clause | effective_date |
| Loan amount appears in the summary table and in a repayment schedule | loan_amount |
Data key format
Choose label values that are descriptive and consistent across your templates. Recommended formatting:
- Use lowercase letters and underscores:
effective_date,loan_amount,borrower_name - Avoid spaces and special characters
- Use names that make sense to an integration consuming the data via API
Auto-population and read-only tags
You can combine auto-population with isReadOnly to create display-only copies of a value. Set the same label on both an interactive tag and a read-only tag. When the recipient fills the interactive tag, the read-only tag reflects the same value without requiring input.
Property support by tag type
The table below summarizes which property categories apply to each tag type.
| Tag type | Basic | Formatting | Visibility | Shared | Template control | Form-fill |
|---|---|---|---|---|---|---|
| Signature | Partial* | No | Yes | No | Yes | No |
| Initial | Partial* | No | Yes | No | Yes | No |
| Text | Yes | Yes | Yes | Yes | Yes | Yes |
| Number | Yes | Yes | Yes | Yes | Yes | Yes |
| Date | Yes | Yes | Yes | Yes | Yes | Yes |
| Checkbox | Yes | Partial** | Yes | No | Yes | Yes |
| Radio | Yes | Partial** | Yes | No | Yes | Yes |
| Dropdown | Yes | Yes | Yes | No | Yes | Yes |
| Attachment | Yes | No | Yes | No | Yes | No |
| Auto-fill: Name | No*** | Yes | Yes | No | Yes | No |
| Auto-fill: Email | No*** | Yes | Yes | No | Yes | No |
| Auto-fill: Date Signed | No*** | Yes | Yes | No | Yes | No |
| Auto-fill: Title | No*** | Yes | Yes | No | Yes | No |
| Auto-fill: Company | No*** | Yes | Yes | No | Yes | No |
| Formula | No*** | Yes | Yes | No | Yes | No |
* Signature and initial tags support isRequired, tooltip, and label. They do not support isReadOnly, placeholder, or text formatting.
** Checkbox and radio tags support backgroundColor and borderColor but not font properties.
*** Auto-fill and formula tags are read-only by nature and do not expose isRequired, isReadOnly, or placeholder. You can set a tooltip and label for identification purposes.
Related articles
- Tag Types — reference for all 15 tag types available in Propper Sign
- Adding Tags to Documents — placement methods, sizing, and alignment tools
- Conditional Tags — show or hide tags based on recipient selections