Skip to main content
Users can configure Text Input fields to accept or restrict the type of data that recipients can enter based on a specific format, style, or number range. These validation settings are configured within the document preparation experience when sending out a signature request or creating, modifying, or utilizing a reusable template.

Configuring text input validation

To configure the Text Input field validation settings within a signature request or reusable template:
  1. Add a Text Input field to the request or template.
  2. Select the Text Input field to configure field settings.
  3. Click to expand the Validation section.
  4. Select your validation option:
    • Predefined validation types: Choose from standard formats like numbers, email, dates, ZIP codes, or SSN.
    • Custom (Regular Expression): Create your own validation pattern for organization-specific requirements. See Custom (Regular Expression) validation for setup instructions and examples.
Field Settings.png
Validation.png
  • Fields configured with text input validation cannot be configured as read-only fields and do not support multiple line data entry.
  • Predefined validations are supported via template tags, but the Custom (Regular Expression) option isn’t supported. For more information on template tags, see Creating Templates Using Tags. For more information on the Custom (Regular Expression) option, see Custom (Regular Expression validation) below.
  • All text input validations are supported via public API. For more information, see the Box Sign API Reference.

Supported validation types

The following table lists the various supported validation for Text Input fields:

Custom (Regular Expression) validation

Beyond the standard validation options, Box Sign offers a Custom (Regular Expression) option to customize validation for fields that need to meet requirements specific to your organization or region. Custom validation uses regular expressions (regex), which are sequences of characters that describe a specific pattern of allowed input for a field.
Custom regex validation is supported through the public API. For more information, see the Box Sign API Reference.

Setting up custom validation

To configure custom validation:
  1. Select Custom (Regular Expression) from the Validation dropdown menu.
  2. Enter your regex pattern in the Regular Expression Pattern field. Provide an Error Message to display when the signer’s input is invalid.
  3. (Recommended) Fill in the Field Name (Label) field to inform signers what data to populate in the field.
Regex.png
Make sure your regex pattern uses a valid and supported format. Otherwise, you won’t be able to apply the validation to the field. You might encounter two input errors: “Invalid pattern” if your regex pattern is invalid, or “Unsupported pattern” if your regex pattern is not supported by Box Sign guidelines. See Regex pattern requirements for supported syntax and limitations. When the signer enters data, the system checks it against your pattern. If the input doesn’t match, the field displays the error message you defined.

Regex pattern requirements

To ensure your custom regex pattern works correctly, follow these guidelines: Supported characters:
  • Unicode letters (\p{L})
  • Unicode numbers (\p{N})
  • Whitespace (\s)
  • Common punctuation: - ( ) . , ' \ / @ _ : % ! ? ^
  • Common international currency symbols: $ € £ ¥ ₹ ₩ ₽ ₺ ₫ ₴ ₱
Box Sign does not support the following regex patterns:
  • Matching back references (\\[1-9])
  • Nested quantifiers (++, **)
  • Lookbehinds ((?<=, (?<!)
  • Recursive and conditional checks ((?R), (?&))

Example regex patterns

Below are useful examples of valid and supported regex patterns:

Phone numbers

Alphanumeric identifiers

Other common patterns

Known limitations

  • Text input validation is not available for CFR Part 11 signature requests or templates.
Last modified on July 8, 2026