Creating users in bulk

For a campaign of any size you will create users in bulk rather than one at a time.

What a user needs

Every user record needs three things beyond their name: a role, an assigned geography, and an account status. The role sets what they can do; the geography sets what they can see. A supervisor assigned at ward level sees that ward and everything below it, and nothing above.

Prepare the upload

One row per person:

• name
• phone_number — used for OTP login where enabled
• role — must match an existing role name exactly
• geo_unit — the unit they are assigned to
• group — optional, for badge printing and reporting

Run the upload

Administration → Users → Bulk upload. As with the hierarchy import, you get a preview and a corrections file for rejected rows.

Credentials

Depending on your configuration, users log in with a PIN, a password, an OTP to their phone, or a QR code printed on their badge. Choose the method before the training session, because it changes what you print.

A note on shared devices

Where devices are shared between shifts, use OTP or QR login rather than saved passwords, and confirm the session timeout is short enough that a handover does not leave the previous user signed in.