> ## Documentation Index > Fetch the complete documentation index at: https://docs.vumasign.com/llms.txt > Use this file to discover all available pages before exploring further. # Filling in before sending > Give a template's answers in the dashboard before it goes out: the same values the API's values and a bulk file's value columns take. When you send one envelope from a template in the dashboard, the send view has two tabs: **Who signs**, for the people, and **Fill in**, for the answers you already know. An offer letter's salary, a start date or a medical plan can go out filled in, so the signer only checks them. This is the dashboard's way to do what the API does with [`values` on create](/api-reference/create-envelope), and what a bulk file does with its `value.` columns ([many envelopes from one template](/concepts/templates-and-one-offs#many-envelopes-from-one-template)). All three take the same answers. Each input shows its data key quietly beside its label, and that key is the name the API and a bulk file use for the same answer. ## What the form shows The form lists every box you may answer, grouped by whose details it holds (see [subjects](/concepts/subjects)) and then by page. | Field | What the form shows | | - | - | | `text` | a text box; a field drawn as printed boxes says how many boxes it has | | `date` | a date picker, with the date written out as the sealed page writes a signing date, for example “1 November 2026”; except a date printed as boxes, one digit in each, which the signer fills in | | `checkbox` | three choices: Signer decides, Ticked, Not ticked | | `dropdown` | a list of its choices; where two dropdowns share a name, only the choices they have in common | | A question (a group of options) | a list of its options, or a tickbox per option where the question takes more than one | | `signer_title`, `signer_company` | not shown: filled from the job title and company you give each person under Who signs | “Signer can change this” starts **on** for every answer you give. A signature, initials, a signing date, and the signer's name and email are never listed: the signer provides those, or Vumasign stamps them when the signer signs. An answer the template itself fixed is shown read-only, as "Fixed in the template". ## Left empty, editable, or fixed * **Left empty:** the signer fills it in. The form says so under each empty box. * **Answered:** the box goes out filled in. The signer sees your answer and can change it. * **Answered, with "Signer can change this" turned off:** the answer is fixed, and the signer sees it but cannot change it. This is `locked: true` on the API. A fixed answer must suit its box. A fixed email address that is not an email address, for example, is refused before you can send, because the signer could never correct it. An answer the signer can change is only flagged, because they can correct it themselves. ## Someone the form is about A subject the template marks as conditional, such as a spouse, has an **On this form** switch. While it is off, that person's boxes are hidden and nothing you typed for them is sent. Switch it on to fill in their details, as the signer can on their own page. ## The same rules as the API The form checks each answer as you type, using the same function the API uses to judge `values` and the same check a bulk file's cells get. A choice must be one of the box's options, a date must be a real day, and a value split across printed boxes must fit in them. So an answer the form accepts is one [`validate-values`](/api-reference/validate-template-values) would accept too. One check needs the document's font, so it runs when the answer is saved, a moment later: whether every character can be printed. If one cannot, the form says so under that box. ## Saving Answers save as you type. A fixed answer is saved straight away. An answer the signer can change belongs to whoever fills that role, so it is saved once the people under **Who signs** are saved. **Send…** saves both before the Send dialog opens, and the dialog says how many answers go out filled in. If someone else changes the same envelope's answers in another tab, your save is refused and you are asked to reload, rather than one of you overwriting the other. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.