Add people manually, from a file, or from a connected source

Open your certificate set and choose People.

• One by one: type a name and email. Good for a handful of people.
• File upload: CSV, Excel (.xlsx) or JSON, up to 5,000 rows and 10 MB per file. Nyvarra shows you each row before anything is saved, and flags missing names or invalid emails.
• Google Sheets or your registration form: keep the list in sync as people register. Available on Campus, Organization and above.

Before you confirm, Nyvarra can tidy the file for you: title-case names written in capitals, fix email formatting and common typos like gmial.com. Every change is shown next to what the file said, and you can keep any row as written. Your file itself is never changed.

Extra columns, such as a registration number or a score, can be printed on the certificate. See Put names and other details on the certificate.

Prepare a file that can be reviewed reliably

Use one header row and one certificate assignment per row. Keep names in the spelling recipients expect, and email addresses in their own column. Store registration numbers as text if leading zeroes matter. Avoid merged headings, totals and explanatory notes inside the recipient table. CSV, Excel (.xlsx) and JSON are supported; older .xls workbooks should be saved as .xlsx or CSV first.

The file limit is 10 MB, with up to 5,000 rows and 100 columns per import. An Excel workbook can contain up to 10 worksheets. Choose the worksheet and header row containing the actual list. A password-protected workbook must be saved as an unprotected copy before it can be imported.

Map, clean and review before committing

1. Open People → Import people. Upload the source and choose its worksheet and header row when needed.
2. Map name and email, then registration number and certificate type if present. Resolve unfamiliar type names instead of assigning everyone to the default accidentally.
3. Decide what to do with extra columns. Keep the details needed on certificates and leave unrelated registration data out of the import.
4. Review cleaning suggestions such as whitespace, email formatting and common domain typos. A suggested correction is not proof that the new address belongs to the person. Preserve unusual names and deliberate capitalization when appropriate.
5. Choose how duplicates should be handled. Skip avoids adding an existing assignment again; Update changes matching details where allowed; a duplicate-error policy asks you to resolve the conflict.
6. Read the row results and fix errors. Confirm the reviewed import, then inspect People and Import history to verify what was actually saved.

People and certificate assignments are different

One person may need a participant certificate and a speaker certificate. That is not necessarily an accidental duplicate: it is two certificate assignments. Some workspaces offer a grouped People preview that shows the person once with multiple types. Check the selected type before removing an apparent duplicate.

Recover from a failed or interrupted import

A preview is not an import. If the connection breaks during confirmation, open People → Import history and inspect that run before uploading the same file again. Resume an available preview or retry the existing operation as directed. If the preview is incomplete or unavailable, upload the original file again and inspect duplicate handling before confirming.

For missing columns, check the header row and worksheet. For incorrect accents, export the spreadsheet as UTF-8 CSV or use .xlsx. For a rejected file, remove password protection or save a clean workbook containing just the required sheet. For a missing certificate value, inspect data fields, not just the name and email mapping.