Step-by-step guides · Help Center
Bulk issuing by CSV, without the scares
How to deliver hundreds of credentials at once, what the system checks before issuing, and what to do with the ones left out.
Prepare the file
A CSV with two required columns: name and email. That is all.
- Export from your student system to CSV, with headers in the first row.
- Check the emails: a mistyped address is a credential that never arrives.
- Write the names exactly as you want them signed, with correct accents and capitals.
Heads up: Accents must be UTF-8. If your system exports in another encoding, open it and save it again as CSV UTF-8 before uploading.
The step that prevents disasters
Uploading the file issues nothing yet. First we show you the report: how many will go out, who is left out and why.
- Rows with an invalid or empty email: discarded, and we list them for you.
- People who already hold that same credential: skipped, so nothing is duplicated.
- If your allowance is not enough, we tell you beforehand, with the exact shortfall.
What to do with the skipped ones
The list of duplicates skipped is not an error: it is the rule that a person cannot hold the same credential twice. But sometimes you do want to reissue — a name changed, a date was corrected.
You can select them from the same report and reissue in bulk. When you do, earlier versions are revoked automatically and only the new one stays valid.
After issuing
- Check the Log: every send is recorded there with its date and result.
- Under Credential holders you see who has claimed and who has not. For those who have not, you can resend the email with one click.
- If you spot an error in several, revoke them from each person's profile and issue again with corrected data.
Heads up: A share of people never open the first email. Resending after three days lifts claim rates noticeably, and it costs no allowance: resending is not reissuing.