---
title: Signing
description: The signer opens a link on a phone, reads the document, fills in their own fields and signs. No account, no app, in their own language.
---

# Signing

The signer opens a link on a phone, reads the document, fills in their own fields and signs. No account, no app, in their own language.

## What the signer sees

The page opens on the document, not a login screen. A bar at the bottom shows how many fields are left, a button jumps to the next one, and the person types a name, draws or types a signature, ticks that they agree to sign electronically and presses Finish. Only their own fields can be changed; the rest is read-only.

## Every role has its own page

A signer signs. An approver approves or rejects with a comment. A viewer opens the document and confirms they have read it. An assistant fills in fields on someone else's behalf and saves them. A person who cannot sign can pass the document on to someone else, and every pass is written into the record.

## If something is wrong

A signer can decline and say why, ask for changes, or save what they have filled in and come back later from the same link. An access code can be asked for before the document opens.

## Fourteen languages

The signing page, the emails and the certificate can be in English, Spanish, French, German, Portuguese, Italian, Dutch, Polish, Turkish, Russian, Arabic, Japanese, Chinese or Korean, and Arabic reads right to left. Eight of the thirteen translations (Spanish, French, German, Portuguese, Italian, Dutch, Polish and Russian) passed an automatic review with a second reading and a back-translation; none has been read by a native speaker yet, and the other five are machine-written drafts marked Beta.

## A worked example: a permission slip on a phone

A parent opens the email on their phone. The page shows the permission slip, a bar says four fields are left, and the Next button jumps to the first. They type their child's name, tick the two checkboxes, draw a signature with a finger, tick that they agree to sign electronically and press Finish. The page says it is done, and the sealed copy reaches them by email when the last person has signed. It took about a minute and no account.

## Built for a small screen first

The signing page is designed for a phone, and widens for a tablet or desktop. Buttons are large enough to press, fields scroll into view as the person moves through them, and what they have typed is kept if they come back later.

## Fields check themselves

A required field stops the person from finishing until it is filled, and a text field with a rule, such as a number or an email, says what is wrong. The server checks the same rules again, so a bad value cannot get through by skipping the page.

## Other people on the same document

Each person sees only their own fields as editable. A person who is not yet up is told whose turn it is. A person who cannot sign can pass the document on, and the record keeps both names.

## Questions people ask

**Which browsers work?**

The signing page is built for current browsers on phones, tablets and desktops.

**How does a signer get their copy?**

By email. Everyone who signed receives the sealed PDF when the last person signs; the "you have signed" page tells them so.

**What if the signer's language is not the sender's?**

Each person can read the page in their own language; the document keeps the language the sender chose.

**Is a typed name a signature?**

Yes. The person chooses to draw or type, agrees to sign electronically, and the record keeps what they did and when.

## Keep reading

- [Sending](/product/sending)
- [Proof](/product/proof)
- [Templates](/product/templates)
- [Use cases](/use-cases)
- [Trust](/trust)