Importing Users

Organisation admins can bulk-import users from a spreadsheet. Runnit suggests how your columns map to user fields, lets you preview every change before anything is saved, and supports rolling back the most recent import if needed.

Before you start

• You must be an admin or owner of the organisation you’re importing into.
• Imports always run in the context of the organisation you’re working in.

Supported files

Format	Extension
Excel	.xlsx, .xls, .xlsm
CSV	.csv

Maximum upload size is 50 MB per file.

The import workflow

1. Open Organisation Users and click Import Users.
2. Upload your spreadsheet. Runnit parses every worksheet and suggests column-to-field mappings for you.
3. Review the suggested mappings and adjust any that aren’t right.
4. Refresh the preview if you changed the mappings.
5. Review the preview: it shows how many rows will be inserted, updated, left unchanged, or skipped, along with row-level detail.
6. Click Commit when you’re happy with the preview.
7. If you need to undo the import, run Rollback Latest Batch.

How mapping works

Runnit infers mappings automatically, and your manual overrides always take priority. Columns you don’t map are simply ignored.

Note

You can flag any unmapped column as a Long Bio Source. The content of those columns is preserved and used to compose each user’s long biography when you commit.

How records are matched

• Email is the unique identifier. All emails are normalised to lowercase before matching.
• Existing users are updated only for mapped fields that contain a value, blank cells never overwrite existing data.
• New users are created and added to your organisation.

Defaults for new users

• New users are set to accept new projects.
• Organisation membership is active, using the role from your spreadsheet if one is mapped and valid, otherwise member.

Preview, commit, and rollback

The preview classifies each row so you know exactly what will happen:

Outcome	Meaning
insert	A new user will be created.
update	An existing user will be updated.
noop	No change needed.
skip	The row will be skipped.
error	The row can’t be processed as-is.

Committing applies all rows together and records a snapshot of every change. As part of the commit, Runnit composes or refreshes each imported user’s long bio from their profile fields (plus any Long Bio Source columns), then refreshes their profile so the new bios are searchable.

Rollback undoes the most recent committed batch for the organisation. Inserted users and memberships are removed, and updated records are restored to their previous values from the saved snapshot.

Tip

Large files take longer to parse and map. If automatic suggestions aren’t available, you can still map columns yourself and import as normal.