# Xodo sign (formerly Eversign) Xodo sign (formerly Eversign) is all about boosting your business workflow and efficiency, and getting day-to-day tasks like scanning, printing and manually signing out of the way. To start with Xodo sign (formerly Eversign) delivery, choose the `Xodo sign(formerly Eversign)`option from the list of deliveries available in the `Deliveries` tab ![](https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FiAGeE29iGoAYj5kiHdvF%2F1680100751285.jpeg?alt=media\&token=a2a82c4e-bc1f-4813-8990-a89f1de68d66) ![Xodo Sign (formerly Eversign) delivery configration](https://191679573-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LDwD-wIOendMUiQ8uVr%2F-M5vdPU7OdiONFrzHXs3%2F-M5vdqJGJVyyJFkl5taS%2Fsignnow.JPG?alt=media\&token=a6dbb17b-b5f1-43e5-8379-b0cea3619754) ## Hidden Tags Hidden Tags is a feature that allows text to be used in documents as a placeholder for signature, initial and other tags for a particular signer. ![](https://191679573-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LDwD-wIOendMUiQ8uVr%2F-M5vbDimbKZMckpLOiT9%2F-M5vbomq3jYj347bSary%2FCapture.JPG?alt=media\&token=e7bddd74-c2b1-4010-980a-3fa210bbc288) ### Usage A hidden tag is a text element wrapped in square brackets `[ ]` containing a series of options in a specific order, all divided by `|` symbols. You can specify a total of 9 options, such as field type, signer ID, required/non-required, field label, field identifier, and more. {% hint style="info" %} Only the first three options are mandatory!\ \ Signer1 \[sig|req|signer1]\ Full Name \[text|req|signer1]\ Date \[date|req|signer1]\ \---------------------------------------------------------------\ Signer 2\ \ \[sig|req|signer2]\ Full Name \[text|req|signer2]\ Date \[date|req|signer2] {% endhint %} {% hint style="warning" %} White-on-White:\ Since hidden tags should in fact be hidden on your document, they should be added in same color as the background of your document. In most cases, this is white-on-white. {% endhint %} **Example:** Here's a hidden tag using all available options: ``` [text|req|signer1|Name|name_1|Paul McSign|125|50|letters_only] ``` In the example above we are creating a required 125x50px text field, prefilled with the value "Paul McSign", with "letters\_only" field validation enabled. Additionally, the field label is set to "Name" and the field identifier is set to "name\_1". **Options:** Below you will find all 9 available options explained: | Order | Name | Description | | ----- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | Field Type | Enter your preferred field type. \[Example: `sig` for Signature] | | 2 | Required / Non-Required | Enter `req` for required or `nonreq` for a non-required field. | | 3 | Signer Number | Enter `signerX` with `X` being the number/ID of the signer this field is for. \[Example: `signer1`] | | 4 | Field Label | Enter your field label. This will be displayed as the placeholder for text fields. \[Example: `Name`] | | 5 | Field Identifier | Enter your field identifier. \[Example: `signature_2`] | | 6 | Prefill Field Value | Enter a value to prefill your field with. Different field types come with different prefill options | | 7 | Field Width Override | By default, your field will come with the same width as your hidden tag. You can override this width by entering a pixel width here. \[Example: `125`] | | 8 | Field Height Override | By default, your field will come with the same height as your hidden tag. You can override this height by entering a pixel height here. \[Example: `50`] | | 9 | Field Validation | Enter your preferred field validation type, if any. | ### **Field Types** The following field types can be created using hidden tags. "Prefill Value" refers to the type of value your field can be prefilled with. | Field Type | Context | Prefill Value | | ---------- | ----------------- | ---------------------------------- | | `sig` | Signature field | | | `init` | Initials field | | | `text` | Text field | String | | `date` | Date Signed field | | | `check` | Checkbox field | 0 for un-checked and 1 for checked | ### **Field Validation** There are 3 types of field validation that can be enabled: * `letters_only` Requires the given field value to contain letters only. * `numbers_only`: Requires the given field value to contain numbers only. * `email_address`: Requires the given field value to be a syntactically valid email address. {% hint style="info" %} Skipping Options:\ In order to skip an option, simply leave it empty without making any changes to the order of other options. A field with a field identifier but without a field label would look like below.\ \&#xNAN;**\[text|req|signer1||name\_1|...]** {% endhint %} ### Optional Recipients & Signers Enabling optional recipients in the Xodo sign delivery will skip **invalid signers** and **carbon copy** (cc) entries. ![](https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FVBVabtAe2m4OQcNzUaqx%2Fimage.png?alt=media\&token=b6e4a4af-e7d4-4af1-8d6d-f6bbd77aeaf4) --- # Agent Instructions: 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: ``` GET https://help.docupilot.app/deliveries/eversign.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.