--- title: "Signature Control" slug: "signature-control" updated: 2025-12-11T02:48:45Z published: 2025-12-11T02:48:45Z canonical: "docs.processmaker.com/signature-control" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.processmaker.com/llms.txt > Use this file to discover all available pages before exploring further. # Signature Control The Signature control allows the Request participant to sign and her or his signature in a Screen. The entered signature automatically saves, but is not committed until the signer submits the Screen. The signer may undo the entered signature prior to submitting the Screen. The submitted signature is recorded as a PNG image that may be referenced from an [Image](/v1/docs/image-control) control by [referencing the Signature control's **Variable Name** setting value](/v1/docs/image-control#render-image-from-a-variable-name). > This control is only available for Form-type Screens. See [Screen Types](/v1/docs/screens#screen-types). Watch the following product tour to learn how to use a Signature control. [Embedded content](https://app.supademo.com/embed/sK-JB1W2DRL0lhYFRlcRE) --- ## Add the Control to a Screen **Permissions** Your user account or group membership must have the following permissions to design a Screen unless your user account has the **Make this user a Super Admin** setting selected: - Screens: Edit Screens - Screens: View Screens See the [Screens](/v1/docs/permission-descriptions-for-users-and-groups#screens) permissions or ask your Administrator for assistance. Follow these steps to add this control to the Screen: 1. [Create a new Form-type Screen](/v1/docs/create-a-new-screen) or [edit an existing one.](/v1/docs/manage-screens#edit-a-screen) 2. From the Controls Menu on the left, expand the **Input Fields** category, and then locate the **Signature** icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/1a738981-1118-42a8-a2c5-087ceffa904d.png). 3. Drag and drop the control to the Screen Builder canvas. Existing controls in the Screen will adjust positioning based on where you drag the control. ​ ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/8c90d4f6-cd95-41bf-ae3d-fbb1005b5356.png) 4. Configure the Image control. See [Settings](/v1/docs/signature-control#settings). 5. Validate that the control is configured correctly. See [Validate Your Screen](https://processmaker.gitbook.io/processmaker/designing-processes/design-forms/screens-builder/validate-your-screen#validate-a-processmaker-screen). Below are digital Signatures to approve a request. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/7ab18338-97f0-4d72-814c-08fea8ddff47.png) --- ## Settings The Signature control has the following configurable settings in the Properties Panel: - [**Variable** panel](/v1/docs/signature-control#configuration-panel-settings) - **​**[**Configuration** panel](/v1/docs/signature-control#configuration-panel-settings) - [**Advanced** panel](/v1/docs/signature-control#advanced-panel-settings) --- ### Variable Panel Settings Expand the **Variable** panel from the Properties Panel on the right to configure the following properties: #### Variable Name Enter the alphanumeric name that identifies this [Screen](https://processmaker.gitbook.io/processmaker/designing-processes/design-forms/what-is-a-form). This field is required. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/309f5ac3-7509-4d0b-9c40-b5e085432fd8.png) Use the **Variable Name** setting value in the following ways: - Reference this control by its **Variable Name** setting's value. The **Data Preview** panel in Preview mode corresponds the Signature control's textual content with that Textarea control's **Variable Name** value. In the example below, `SignatureControl` is the **Variable Name** setting's value. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/5c2cbf4d-e9d0-47c7-b729-0541f690f6a0.png) - Reference this control's value in a different Screen Builder control. To do so, use [mustache syntax](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/mustache.5(12).html) and reference this control's **Variable Name** value in the target control. Example: `{{ SignatureControl }}`. - Reference this value in [**Visibility Rule** setting expressions](/v1/docs/signature-control#visibility-rule). See [best practices](/v1/docs/screen-design-best-practices#naming-request-variables-for-processmaker-screen-controls) when editing a Request variable name. #### Required Select the **Required** setting to clarify that the signature is required to submit the form. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/3733fa96-921f-44fb-a717-8c44cd7aae7f.png) --- ### Configuration Panel Settings Expand the **Configuration** panel from the Properties Panel on the right to configure the following properties: #### Pad Height Set the vertical spacing of the Signature control's pad: the space into which the signature is entered. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/0903530a-a896-4cf6-b247-cde2a631bef8.png) The height may be set in any of the following units: - em unit, based upon the relative font-size of the parent font size (em) - inches (in) - percentage (%) - pixels (px) - relative to the viewpoint's height (vh) - relative to the viewpoint's width (vw) - rem unit, based upon the font-size value of the root element (rem) **100px** is the default height setting. If the entered value is not in the correct format, the following validation error displays: **The Pad Height format is invalid.** --- ### Advanced Panel Settings Expand the **Advanced** panel from the Properties Panel on the right to configure the following properties: #### Visibility Rule[](/docs/signature-control#visibility-rule) Specify an expression that indicates the condition(s) under which this control displays. See [Expression Syntax Components](/v1/docs/feel-expression-syntax#show-or-hide-screen-builder-controls). If this setting does not have an expression, then this control displays by default. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/9b4922f7-c5a2-4105-b212-d281ad5c942c.png) For example, this control displays if the variable value **tip** is **1**. For a detailed example of the Visibility Rule setting, see [Show or Hide Controls Based on Button Selection](/v1/docs/example-show-or-hide-controls-based-on-button-selection). Note the following regarding how to use visibility rules: - To make this control hidden until another control contains a value, enter the **Variable Name** setting value of that control to this control's **Visibility Rule** setting. - [Visibility rules override custom CSS settings](/v1/docs/screen-design-best-practices#visibility-rules-override-custom-css-settings). #### Device Visibility[](/docs/signature-control#device-visibility) Select on which device types this control displays: - **Desktop:** The control displays only on desktop devices. Enable the **Show for Desktop** toggle key. - **Mobile:** The control displays only on mobile devices. Enable the **Show for Mobile** toggle key. - **Both:** The control displays on both desktop and mobile devices. Both toggle keys are enabled by default. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/2a3e0b96-3066-4466-9ca0-8bf348429f4c.png) #### CSS Selector Name[](/docs/signature-control#css-selector-name) Enter the value to represent this control in custom CSS syntax when in [Custom CSS](/v1/docs/custom-css#add-custom-css-to-a-processmaker-screen) mode. As a best practice, use the same **CSS Selector Name** value on different controls of the same type to apply the same custom CSS style to all those controls. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/c7e1600b-e145-47ba-a39d-3ac4c9bc41c9.png) Then, use this name in the [Custom CSS](/v1/docs/custom-css#apply-css-to-specific-processmaker-screen-controls) feature to apply CSS styling to this control as follows: ```plaintext [selector='Submit Form'] {    color: blueviolet; } ``` See the following best practices regarding custom CSS in Screens: - [Editing a CSS name to represent this control in custom CSS syntax](/v1/docs/screen-design-best-practices#css-selector-naming-best-practice) - [Visibility rules override custom CSS setting](/v1/docs/screen-design-best-practices#visibility-rules-override-custom-css-settings)