Skip to content

Setup checklist

This checklist takes a brand-new account from empty to processing its first certificate. Follow the steps in order — each one builds on the last. The whole path is usually done by an Admin or Account Owner, but several steps are handed to other roles, and we call out who does what so nobody waits on an action they cannot perform.

Different roles own different parts of setup. Skip to your steps if you are not an admin — and don’t worry if the others are greyed out for you; that is expected.

Step Who does it
1. Secure your login Everyone (your own account)
2. Invite your team Account Owner / Admin
3. Create an organisation Admin (or Project Manager)
4. Create your first material Admin / Project Manager
5. Build a definition & map Admin / Technician
6. Process a test certificate Submission Coordinator to prepare; QP / Admin to sign

Do this first, before you invite anyone else.

  1. Set up an authenticator app so a code is required alongside your password. See Authenticator app (TOTP).
  2. Save the backup codes DASH shows you — they are displayed only once. See Backup codes.
  3. Optionally register a passkey for password-free sign-in. See Passkeys.

Account Owner / Admin.

  1. Invite each colleague by email and assign the right role. See Team management.
  2. Give people the least they need: Technicians for building maps, a Quality Person for signing, Submission Coordinators for preparing certificates. Review the options in Roles & permissions.

Admin (or Project Manager).

Create the client organisation you produce data for. This is the record your materials and certificates will hang off. See Create & edit an organisation.

Admin / Project Manager.

Run the guided wizard to create a Material (Project) for your first product or data stream. You will link it to the organisation from step 3 and set up its data channels along the way. See Create a material (wizard).

Admin / Technician.

  1. Create a Definition — the data structure your records follow — and add its properties. You can speed this up by importing them from a sample CSV or XML. See Create a definition and Import properties.
  2. Create a Definition Map to translate an incoming file onto that Definition, then add your field mappings and validation rules. See Create a definition map and Validation rules.
  3. Test the map against a sample file before you rely on it. See Test with a sample.

Now put it all together with a trial run.

  1. (Submission Coordinator, Technician or Admin) Create a certificate for your material, choosing the definition and map and uploading a sample file. See Create a certificate.
  2. (Submission Coordinator or Admin) Review the mapped data and send it for approval. See Review & edit and Send for approval.
  3. (QP, Admin or Owner) Sign the certificate. See Sign a certificate.

With one material, definition, map and test certificate in place, you have proven the whole pipeline. To automate incoming data so certificates arrive without manual uploads, move on to Automated ingestion.