Issuing in bulk
Upload a spreadsheet, see what will happen, then commit.
Upload an .xlsx or .csv with one row per recipient and one column per variable the programme
asks for.
It is checked before anything is written
The preview names every problem row and says what is wrong with it: a missing required value, a date that is not a date, a character the document font cannot print. Nothing is created until you commit.
This is the part that makes bulk issuing safe rather than frightening. A two-hundred-row sheet with four bad rows tells you about the four, rather than issuing a hundred and ninety-six and leaving you to work out which.
Duplicates
A recipient is matched on email. Whether a second credential to the same person in the same programme is allowed is a switch on the programme.
After the upload
Rows become credentials in PENDING, or UNDER_REVIEW if the programme requires approval. Nothing
has been published, billed or emailed. Review the batch, then publish it — as a batch, or
individually.
Scheduling
A batch can be scheduled to publish at a future moment. Credits are consumed at fire time, not when the schedule is made — so a schedule can fail on an empty balance, and when it does nothing is published and you are told. Reserving credits for work that may never happen would be the other choice, and it is worse.