Using the program — Bulk import and the CSV template

Where: Keys → Bulk import (or Tools, same window).

Use this when you have many keys. Use single Import a key when you have one file or one paste.

What you can feed it

  • One or more .asc, .pgp, .gpg files
  • A folder (scan; drag-and-drop onto the bulk window if enabled)
  • A ZIP of those files (the zip is checked before keys are stored)
  • A CSV that matches the template

CSV template

The template ships in the Help folder:

Help\ngwe3-bulk-import-template.csv

Copy it, keep the header row, add one key per line.

Typical columns:

  • name — label in the sheet (does not replace the user ID inside the key)
  • email — optional
  • file path — full path to an .asc / .pgp / .gpg on disk
  • armored — the full BEGIN PGP … KEY BLOCK text when you are not using a file path
  • group — stored on the key if import applies groups (e.g. Financial)
  • notes — stored as notes when the importer supports notes
  • armored (flag) — whether the armored column is used

Use either a file path or an armored block. A path with no file fails that row. An armored column must include the complete block, not a truncated line. Group and notes are extra data in the vault; they are not written into the OpenPGP key itself.

Dry-run

  1. Add files, folder, zip, or CSV.
  2. Run dry-run (preview) before import.
  3. Read each row: import, skip duplicate, expired, revoked, weak algorithm, missing encrypt or sign capability, public-only vs secret, malformed.
  4. Only then run the real import.

Dry-run does not change the key store.

After import

  • Duplicates stay skipped.
  • Open the grid, filter by group if you set one.
  • Verify fingerprints before Verified.
  • Weak/1024 keys are not used for encrypt even if a row appears.

If it fails

  • CSV: armored text not recognized — put the whole block in the armored column, or use a file path instead.
  • Many skipped, one duplicate — those keys are already in the store or failed a check; read the status column.
  • ZIP invalid — use a clean zip of key files only.
  • IO error on a path — the file moved or the path in the CSV is wrong.

Next

Recipient groups if you used the group column. Encrypt a test file to one imported public key only after you check the fingerprint.