> ## 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.

# Bulk send from the dashboard

> Send one template to everyone in a spreadsheet: match its columns, check every row, see what it costs, and follow each envelope.

**Send in bulk**, under **Envelopes**, turns each row of a spreadsheet into its own envelope from
one template. It is the dashboard's way to send a batch. A program sends one through
[`POST /api/v1/envelopes/batches`](https://docs.vumasign.com/api-reference/create-envelope-batch) instead.

## 1. Upload

Choose the template. If your organisation has more than one brand, choose one under **Send as**. A
standing authorisation must belong to the same brand, so the brand decides which ones are offered
(see [standing authorisations](https://docs.vumasign.com/concepts/standing-authorisations.md#in-the-dashboard)).

**Download a starter spreadsheet** gives you a file with one column for each person's name, email and
mobile, and one for each named field, as CSV or as an Excel workbook (.xlsx). Fill in one row per
envelope and upload it.

Upload an Excel workbook (.xlsx) or a CSV, of up to 500 rows and 1 000 KB. A
workbook with several sheets starts on the first and lets you choose another. In a workbook, a date
cell is read as that date, a number as the number stored in the file, and TRUE or FALSE as a ticked
or unticked box. A formula is read as the value your spreadsheet last saved for it: nothing in the
file is calculated or run. An old Excel file (.xls), or one with macros (.xlsm), is refused: save it
as .xlsx or CSV first.

## 2. Match columns

Your own column headings are matched to the template by name, so "Start date" fills the field called
Start date. Check the matches and change any that are wrong. A column you do not need is marked
**Not used**.

You also choose, for each role:

* **Who it is.** Either the person named on each row, or the same person on every row (an HR manager
  who approves every contract, for example).
* **How we confirm them.** Choose Signing link only, Email code or
  Mobile code for every row, or take it from a column whose cells say `link`,
  `email` or `mobile`. A mobile code goes to the number in the mobile column, which must be a South
  African mobile number. If you choose nothing, the role uses the check set on the template.

An owner or admin can also have a role signed under a standing authorisation on every row: choose
**Pre-sign as …** for that role before downloading the file. The authorisation fills in that role's
person, so the file has no columns for it. Any answers that role needs must still come from the file
on every row, and they are locked, because a standing authorisation applies a signature but never
chooses an answer.

## 3. Review

Every row is checked with the same rules as a single send: email addresses, mobile numbers, required
people and fields, each cell's value, and the same people appearing on two rows. A row that would be
refused is marked **Needs attention**, with the reason. **Fix** lets you edit that row's cells, and
**Skip** leaves the row out. Send stays off until no row needs attention.

The **Cost** panel works out the price from your plan and this month's usage. It shows the envelopes
your plan still includes, the extras at your plan's rate, and an estimate of mobile codes (one for each
signer asked for a mobile code). No more than 300 mobile codes are sent to phones for one
organisation in a day, as a safety limit. If this batch would go over that limit, Review warns you
before you send it. On a plan
that stops when its allowance runs out, the panel tells you how many envelopes can still go out. Any
envelope over the allowance is not sent; it stays a draft, with the reason.

Give the batch a name, so you can find it again under **Send in bulk**.

## 4. Send and results

Every envelope is created as soon as you press Send. If any row would be refused, nothing is sent at
all. The envelopes then go out one at a time. A small batch finishes while you wait. A large one opens
its own page, which shows the count as envelopes go out. You can close that page: sending carries on
without it.

The batch's page lists every row with its status, and links to each envelope. A row that was not sent
says why and keeps its draft. If a row fails to send 3 times because of a fault on our
side, it is marked not sent, and you can send its draft from the envelope list.

* **Remind everyone who hasn't signed** sends a reminder to each person still due to sign. Your
  organisation's limit on reminders applies, and anyone who was invited or reminded in the last
  1 day is skipped, so pressing it twice reminds nobody twice.
* **Download results (CSV)** saves the rows as the page shows them. Any cell that a spreadsheet would
  read as a formula is written as plain text instead.
* **Withdraw the batch** asks you to confirm first. It stops sending the rest of the batch and voids
  every envelope that is still out for signature. Envelopes that are already signed stay signed.

## Related

* [Templates and one-offs](https://docs.vumasign.com/concepts/templates-and-one-offs.md)
* [Signer verification](https://docs.vumasign.com/concepts/signer-verification.md)
* [Standing authorisations](https://docs.vumasign.com/concepts/standing-authorisations.md)
* [Pre-signed salary letters](https://docs.vumasign.com/guides/salary-letters.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.