Skip to content

Send a document for signature

Sending a document takes four steps, always in the same order. The wizard will not let you move on while the current step is incomplete — Next stays disabled.

New document first asks “Who is going to sign? The answer decides the path.” This page is the Send for signature card — “For a document other people sign too. Choose who, the order and how each one signs.” — and its Prepare to send button. If the document is yours alone, the other card, Sign it myself, now, takes three steps instead of four: see Sign a document yourself. Below the two cards, if your organisation has templates, Or start from a template takes you to the templates list.

# Step What it is for
1 Add Documents Add documents for signature
2 Recipients Who receives this document and how they sign
3 Prepare Documents Prepare annotations on the documents
4 Review & Send Recipients, message, deadline and resources — then send

In the Add Documents and Prepare Documents steps, the footer has Save draft, so you can come back later. The wizard also saves by itself — you will see “Auto-saving draft…”.

Drag the files in or use Select files. It accepts PDF/DOCX, up to 128 MB per file.

The first wizard step, with the file upload
area.

You can add more than one file. They travel in the same process and are signed together — anyone on copy receives the complete set of documents. On a computer, with two or more files, drag them by the handle to change the order of the documents; clicking a file’s name renames it.

Below the list sits the Dossier card, with the Group into a process switch. It is only active with two or more files, and switches itself on when you add the second. When on, it asks for the Process name — “E.g. Lease agreement” — and Next will not move on without it: “Enter the process name to group the documents.”

A Word file is converted to PDF, and it is the PDF that gets signed — the file is marked Converted to PDF. Check it before moving on: pagination can shift during conversion.

On a free organisation, this is where the draft is created — and the free plan allows 5 at a time. With 5 drafts in progress, Next opens Draft limit reached, and See drafts opens the list in another tab. The file stays in the list: after you send or delete a draft, press Next again. See Five drafts at a time.

This step decides the two things that matter most: who is involved and how each person takes part.

Add the people involved, choose who signs and who only receives a copy.

When you reach this step a short video opens, How to add the people who sign, recorded on desktop only. Like the step 3 one, it opens again each time until you tick Don’t show again.

The recipients step: the Signing order selector above, and one row per person
with name, email, phone, activity and the customise
button.

Each person is a card. On its top line, left to right:

Element What it does
⠿ and the number Drag to change the signing order — sequential mode only
Name · Email · Phone number The person’s details. As you type the name or email, the application suggests your contacts
List icon, in the name field Pick from your contact list
Up and down arrows Change the order without dragging — sequential mode only
Signs / Receives copy This person’s role
Customise The settings for this person alone — see below. On a phone it is the icon only
Bin Remove the person (not when there is only one)

Underneath, for signers, sit the signature types you gave them, each with its own icon and colour. Clicking one opens the same panel as Customise.

Add opens a menu in two groups: under Recipients, New recipient (a blank row); under Fill recipient, Contact list, My contact info and Import list. If you are already on the list, My contact info is greyed out with “Already in the recipient list”.

Above the list sits Signing order, and this is where you decide whether people sign one after another or all at the same time.

Option What the application says
Sequential “Each person is invited after the previous one signs, in list order.”
All at once “Everyone is invited at the same time and signs in any order.”

Sequential is what you start with. Under it, position in the list is the real order of the process: the number beside the ⠿ is each person’s turn, and anyone whose turn has not come up shows, on the sent document, as Awaiting their turn.

Under All at once that number disappears and the list can no longer be reordered — nobody has a turn. The ⠿ now reads “No order — everyone is invited at the same time”. Everybody gets the email the moment you send, and nobody waits for anybody.

The Customise button opens a panel titled with the person’s name, holding two tabs: Recipient and Message.

The Customise panel, with activity, signature types and recipient
verification.

Activity to perform — Signs or Receives copy. Same as the column on the row, repeated here for convenience.

Signature types — and here is the part that usually surprises people: these are checkboxes, not a single choice. The same person can hold more than one type on the same document.

Option What it is
Simple signature A drawn or typed visual signature
Initials Initials, for initialling pages
CMD - Chave Móvel Digital Qualified signature — see Qualified signatures with CMD
SCAP - CMD with professional attributes Qualified, and proves professional capacity
LDC - Local Digital Certificate Advanced, with the signer’s own digital certificate — see Sign with your own digital certificate

A new signer arrives with Simple signature and Initials already ticked; if the organisation has CMD balance, CMD as well; and if professional attributes are enabled, SCAP too. That way the next step shows everything you can place, with nothing hidden in a menu. LDC - Local Digital Certificate is never ticked by default: tick it when the person has a certificate of their own. A type with no zones placed is dropped from the send and costs nothing — see How a signature is counted.

Recipient verification — defaults to Organization default: it uses whatever the organisation settings say at the moment the document is sent. You can raise or lower the level for this person alone. The default lives in Configure organisation policies.

The options that appear only without a qualified signature

Section titled “The options that appear only without a qualified signature”

These sections do not appear with CMD or SCAP. Untick them — or choose Local Digital Certificate — and two new sections appear in the panel:

The same panel with a simple signature: 2-Factor Authentication and Confirm ID
Document appear.

2-Factor Authentication — None, SMS Code or Password. The help icon next to the title explains:

Choose the security method used to confirm the signer’s identity. You can require no extra authentication, or request an SMS code or a password.

With SMS Code, the panel shows the person’s mobile number, which you can correct there. With Password, you type the Access password (4 to 8 characters) — you set it yourself and must pass it on to the person by some other channel.

On some subscriptions, SMS Code is greyed out.

Confirm ID Document — Not required or Request Document, with a National ID Card or Passport and the Document number. With Request Document, the signer has to confirm their identification before signing.

With Local Digital Certificate both sections stay. The certificate is not verified by the State the way Chave Móvel Digital is: the SMS code or password is the proof of who opened the link, and the identity document number you enter here is checked against the certificate’s at signing time — see What AssinaJá checks.

The Message tab, with language and private
message.

Language decides which language this person’s email and signing screen use. The private message field — its title is shown in Portuguese, Mensagem privada, with the hint “Private note for this recipient (optional)” — adds text only this person reads, useful for instructions that do not concern the others.

What the wizard blocks, and what it only warns about

Section titled “What the wizard blocks, and what it only warns about”

Blocks: moving on without at least one person who Signs. The Next button stays disabled, with no message, until there is a signer and every row has a name, a valid email and a language. With several documents, each signer has to sign at least one, and each document has to have someone signing it.

The phone number on the row is needed only for the SMS code. For Chave Móvel Digital, the signer enters it in the signing wizard.

Nobody is added twice: someone coming from the contact list or an imported list with an email already among the recipients is not added again. You can put yourself in as a signer — with My contact info or by typing your email — with no warning.

The editor step: Prepare annotations on the documents.

When you reach this step, a short video opens — How to place the signature zones — about 14 seconds, looping and silent, with this text underneath:

There are two ways, with the same result:

• On the page, right-click — or, on a phone, press and hold for about a second — then choose Add Signers and the signature type: the zone lands where you touched.

• Or open the Content panel on the left, press the + next to each person’s signature type and drag the zone into place.

You are not signing now — you are preparing the document for the people who will.

Got it closes it, but the video opens again the next time you reach this step — only the Don’t show again box, ticked before closing, stops it coming back. That “seen it” is stored in the browser itself — not in your account — so on another computer, in another browser, or after clearing the site data, the video appears once more. This step has no button to watch the video again; the help in the top-right corner opens the explanation of this step, with the same video at the top.

On narrow screens a different recording is shown, made with a long press instead of a right-click. The gestures are not the same, and the shrunken desktop video did not teach them.

The signature-zone explainer video, open over the step 3 editor.

The editor on arrival, with the Content panel closed on the left and the
document on the right.

On the left sits the Content panel, which starts closed so the document gets the whole width. The button on the closed panel — Content, when you hover over it — opens it.

Once open, it shows the Zones and Auto AI tabs. In Zones, the Fields button opens three groups — Fixed, Dynamic and Fill in — and picking a type places it straight away on the page you are viewing.

Below sits the Add Signers list. Under each person there is one row per signature type you gave them — Initials and CMD in the example — each with:

  • + — add a zone of that type to the document
  • × — remove that type from this signer

Where each person’s first zone appears. With +, each person’s first signature no longer always lands in the same spot:

  • If the organisation has already sent this form — the same document, with the same number of pages and signers — the zone opens where that person signed last time. The same goes for the first initials on each page.
  • On a new form, the signature opens next to the person’s printed name, on a blank line with a word such as Assinatura or Cliente nearby, or at the end of the text on the last page.

It is only a starting position: drag the zone like any other. It may open on another page — the document scrolls there. A second zone of the same type goes to the page you are viewing, as before. The organisation learns when it sends an uploaded document; documents generated from a template already carry the template’s positions and do not count.

The signers themselves — who they are, their name, their email, who leaves — are changed in the Recipients step, not here.

As you place fields, the sections Fixed content, Dynamic content and Fields to fill in appear underneath, listing the fields already placed in each. A section only appears once it has at least one field.

On the right sits the document, with zoom, fit to width and fit to height.

Right-clicking on the page opens a menu at the exact point you clicked:

The right-click context menu, with Add Signers and Fields, and Fields open on
Fixed, Dynamic and Fill in.

Entry What the application says
Add Signers “Signature and initials zones for each person, at the point you clicked.”
Fields “Fixed content, dynamic content or boxes the signer fills in.” — opens Fixed, Dynamic and Fill in

Every entry in the menu, and every type inside it, carries a line of explanation under its name.

It is quicker than dragging, and it puts the zone where the pointer is rather than dropping it by eye. For a contract that needs a signature at the foot of every page, it is the difference between one minute and five.

Once placed, a zone can be dragged and resized by its corners.

Questions the signer fills in while signing

Section titled “Questions the signer fills in while signing”

The Fill in group places boxes on the document that the signer fills in at the moment of signing — a tax number, a start date, a choice between options. They differ from Fixed and Dynamic fields, which you, or the platform, fill in before sending.

Type What the application says
Free text “The signer writes a text; you may limit its length and format.”
Date “The signer picks a date, within the limits you set.”
Number “The signer writes a number; optional decimals and limits.”
Option (choice) “One box of a choice question; several boxes make the group.”
Choice list “The signer picks one entry from a list you define.”
Matrix “A rows × columns grid; the signer marks one cell per row.”

A box’s panel opens on the right, titled with its type, when you press the gear at the box’s corner, double-click the box or right-click it:

A Free text box selected: the panel with Filled in by, the question, Required
and Validation type set to tax number.

  • Filled in by — the person who answers. Each box belongs to one person.
  • Question — the text the signer sees. Up to 200 characters.
  • Required — without an answer, the person cannot complete their signature.
  • Field identifier — “Identifies the answer in the report and the API. Unique in the document.”

And, depending on the type:

  • Free text — Max. characters and Validation type: Any text, Digits only, Letters and spaces only, Letters, digits and spaces, Email address, Tax number (9 digits), Postal code (0000-000) or Other (regular expression). With Other you write the expression, which applies to the whole text; Try with… tells you whether a sample Passes. or Does not pass.
  • Date and Number — Minimum and Maximum; for a number, also Decimal places.
  • Option (choice) — each box is one option, laid over the square printed on the document. Boxes sharing the same identifier make up one question, with Single choice or Multiple choice under Mode.
  • Choice list — the Choices, and at most one Preselected.
  • Matrix — # Rows and # Columns, Result by row or column, Selection with One choice or Several choices, and an optional List of values: “Without a list, the answer is the number of the choice (1, 2, …).”

Who a new box belongs to. In sequential order, to the signer who signs first; in parallel, to the first one in the list. Change it under Filled in by. If you want the same question answered by two people, place two boxes.

Whoever answers must sign. A person with boxes to fill in needs a signature or initials zone in the same document — that signature is what attests the answers. Without it, Next opens Fields to fill in need fixing, with one line per problem — in this case, “[name] has fields to fill in but no signature or initials zone in this document.”

If you remove a signer, their boxes pass to another person who stays.

They cost no credits. A box to fill in is not a signature: it is not charged and does not count in the resource summary of step 4.

What happens to the answers. Each answer is written into the PDF that person signs, where the box is, and is also kept as data — it appears in the completion report and in the API. Other signers only see an answer once the person who gave it has signed, and from then on nobody can change it.

One qualified signature per person, per document

Section titled “One qualified signature per person, per document”

Simple Signature and Initials zones repeat as often as you like, but each person signs with CMD, SCAP or Local Digital Certificate only once per document. The editor refuses a second qualified zone:

Each signer signs with the Digital Mobile Key only once per document. Remove the existing qualified zone before placing another.

The message is the same for a Local Digital Certificate zone. The reason is in Rules to know.

Each zone costs one credit, of that zone’s own type

Section titled “Each zone costs one credit, of that zone’s own type”

The charge is made per zone placed, and each one pays for the resource of its own type — initials cost a simple signature, even for someone who signs with CMD. The full table is in How a signature is counted.

A signer holding visual signatures and CMD does the visual ones first and the CMD last, because CMD seals the document. It is a per-person rule, and only that: it does not require CMD signers to sit at the end of the list, and it does not stop several people signing with CMD at the same time — see Sign a document.

The final step adds no people — those are set in Recipients. It gathers, in cards that collapse:

  • Signature Message — the email’s Subject and Message, pre-filled with a default text you can change, and Send automatic reminders, with the Periodicity. If the recipients use more than one language, Messages by language also appears, for each language’s subject and message.
  • Summary — the documents (or “Dossier: …”, if you grouped them into a process) and the people, with each one’s order and signature types.
  • Signature Deadline — off to start with. Turn on Expiration date to pick the day and time.
  • Resources to consume — what the send will use, with the balance available beside it.

Below the resources, the application already shows the problems Send would run into:

Notice What to do
“Confirm your phone before sending.” Confirm now — see below
“Your balance doesn’t cover this send. You can top up when sending.” You can send anyway: Send opens the purchase — see below
“No signature zone: …. Go back to Signatures.” Back to Signatures

On a free organisation, the summary also has the line Sends to third parties (available / plan) and a note about the send. Sending to someone outside the organisation — to sign or only on copy — uses one send. See What counts as a send.

There is nothing to switch on. Every document published from the wizard carries the platform’s certifying seal, applied before any signature — except documents that arrive already signed. See Secure final document.

On a free organisation: confirm your mobile number

Section titled “On a free organisation: confirm your mobile number”

An organisation on the free plan only sends documents once the person who created it has confirmed their mobile number by SMS. It happens once, and it is there to protect the free plan from accounts created in bulk — “We send a code by SMS to confirm the account is yours. We don’t use your number for advertising.”

If you have not done it yet, pressing send opens One more step before sending — “Once confirmed, sending continues from here without losing anything.”:

  1. Mobile number — your number, with the country code — and Send code.
  2. “We sent the code to {number}. It is valid for {n} minutes.” Type the 6-digit code and Confirm. If it does not arrive, Resend code — available after a moment, with the countdown in Resend in {time} — or Change number.
  3. Mobile number confirmed — “The number is now linked to your account.” Sending carries on by itself from here.

The rule is checked before the send writes anything: nothing is debited and nobody is invited until the number is confirmed. It runs wherever a document goes out — this wizard, Use template, Sign now and the API — and it does not depend on who presses the button:

  • What counts is the mobile number of whoever created the organisation, not the sender’s. A colleague in a free organisation whose Owner has not confirmed yet sees Sending unavailable — “This organisation can only send documents after the account owner confirms their mobile number. Ask them to sign in to AssinaJá and confirm it.” — and confirming their own number changes nothing.
  • Organisations on a paid plan do not go through this. Neither do invited signers: signing is not sending.

You can get ahead of it: the same dialog, Confirm your mobile number, opens once when you arrive in the application with the organisation just created, with Later to close it. After that a reminder stays on the home screen — “Confirm your mobile number to send documents.” with Confirm now — until the number is confirmed. It can also be done from your profile: see The contact has to be validated.

Message What to do
“The number is not valid. Check the country code and the digits.” Check the country code and the number.
“This is not a mobile number. Enter a number that can receive SMS.” Mobile numbers only.
“We don’t send SMS to numbers from this country yet.” Use a number from a served country.
“This number is already linked to another account. If it is yours, contact us.” Each number confirms one account only.
“We sent a code a moment ago. Wait a little before requesting another.” Wait for the Resend in countdown.
“You have reached the limit of code requests. Try again later or contact us.” There is a cap on requests; come back later.
“Too many attempts for this code. Request a new code.” Resend code.
“The code has expired. Request a new code.” Resend code.
“The code is not correct. Check the message and try again.” Check the six digits in the SMS.
“SMS cannot be sent right now. Try again in a few minutes.” A temporary sending failure; not your number.

When you press Send, the application first asks the server what this send is short of — without saving anything. If nothing is missing, the document goes out, with no offer at all. If something is, nobody is invited, nothing is debited, the document stays a draft, and the purchase dialog opens with two packs of each missing resource — the first one already selected, marked Best price when it works out cheaper per unit.

On a free organisation, the dialog sells the packs right there, on Stripe, and brings you back to the draft — for sends and for signatures alike. If more than one resource is missing (sends and CMD signatures, say), it is a single dialog: To send, you need these packs — “Choose one pack of each and pay once. Your draft stays saved.” There is a Pack of … section per resource, the total (“Total: … + VAT”), and Continue to payment opens a single payment for all of them. If one of those resources is not sold that way, the dialog handles one at a time and warns about the rest: “Afterwards we will also ask you for …”. It is all in When the sends run out.

On a paid plan, the dialog is called Not enough balance to finish — “The document was saved as a draft. Choose a pack to continue.” Pick a pack and Buy in the store takes you to Add-ons with that pack in focus, to pay with credits; See more purchase options opens the store; and Back to the draft closes the dialog. After buying, go back to the draft and press send again. If there is no pack on sale for that resource, the dialog says “There are no packs for sale for this resource. Open the store to see the available options.”

The dialog does not close with Escape or by clicking outside.

If you press send again on a document that has meanwhile gone out, the answer is “This document has already been sent. You can follow it in the document list.”

See Plans, credits and extras.

While the platform seals it, the document sits in the list’s In preparation view, with the status Prepare (in the document details, Processing). Then it moves to Waiting for others. When the last signature lands it passes through Finalizing before it is Completed. See Document lifecycle.