On this page

Incident Tracker allows administrators to import data in bulk instead of entering it one record at a time. This is particularly useful during initial setup or when onboarding large groups of users.

You can import:

  • Users (logins)
  • People/Witnesses
  • Locations

Accessing the Import Data Feature#

To begin importing data:

  1. Navigate to Admin > Importing Data.
  2. Select the tab for the type of data you want to import:
    • Import Logins/Users
    • Import People or Witnesses
    • Import Locations

Before You Import#

To import a file:

  1. Click Choose File and select your prepared import file.
  2. Leave Test import file for errors (does NOT import) checked and click Upload to check the file.
  3. Review any errors and make necessary corrections to your file.
  4. Once the file passes the test, uncheck Test import file for errors (does NOT import) and click Upload again to import the data.

Importing Users#

The users import file must be an Excel spreadsheet (.xls or .xlsx). Download the template from the Import Logins/Users tab.

The column headers must be exactly:

firstname | lastname | login | pword | email | submit | myreport | docsview | viewrites | append | docs | edit | label | deleterites | admin
Column Required What to enter
firstname Yes The user's first name
lastname Yes The user's last name
login Yes The user's login
pword No A password. Leave blank to create a third-party login account.
email Yes The user's email address
submit, myreport, docsview, viewrites, append, docs, edit, label, deleterites, admin Yes True or False for each right

Notes

  • The rights columns (submit, myreport, docsview, viewrites, append, docs, edit, label, deleterites, admin) must contain only the text True or False.
  • All fields are required except pword.
  • If pword is blank, the account is created as a third-party login (for Google or Microsoft sign-in).
  • If a password is given, the user must change it when they first sign in. There are no exceptions.
  • No welcome emails are sent during an import.

Example

firstname lastname login pword email submit myreport docsview viewrites append docs edit label deleterites admin
Jane Smith jsmith@example.com jsmith@example.com True True False False False False False False False False

▢️ Interactive Tutorial – Importing User Data#

Post-Import Actions#

After successfully importing users:

  • Assign appropriate user rights and restrictions to each new user.
  • Inform users of their login credentials and any necessary setup steps, since no welcome emails are sent.

Importing People/Witnesses#

Download the template from the Import People or Witnesses tab. The columns are:

id | name | info
Column Required What to enter
id No An identifier for the person
name Yes The person's name
info No Details about the person. HTML markup is accepted.

Notes

  • Only name is required. id and info are optional.
  • The info field accepts HTML markup. For example, use \ to put info on separate lines and ** for bold.

Example

id name info
061tpz Donna Seaworth **Donna Seaworth**; Role: Reporting Party

Importing Locations#

Download the template from the Import Locations tab. The columns are:

location | sublocation | room
Column Required What to enter
location Yes The main location
sublocation No A sub-location within the location
room No An area or room within the sub-location

Notes

  • Only location is required.
  • Each row is one full location path.
  • Row structure matters, because the 2nd and 3rd drop-downs in Incident Tracker depend on the first selection. Repeat the location (and sub-location) on every row.

Example

location sublocation room
Gotham City Stark Tower 101
Gotham City Stark Tower 237
New York Kennedy Building 140