Filling out the User Data Import Template

Each row is dedicated to a single user. For the most part this is straight forward and self-explanatory to fill in. FIRST_NAME requires the user’s first name; USERNAME requires their username and so forth. 

Setting users’ roles:

To assign a user as a standard user simply ignore the ROLES column and fill out the other required information.

To assign a user the role of Manager, use that person’s email address in SUPERVISOR_USERNAME column when filling in the data of the users for whom they are managers. The ROLES column doesn’t need any data when filling out the row for the desired manager.

To assign a user as an administrator, enter “Administrator” in the ROLES column. So, the ROLES column is only used for administrators.

For each user you can select the reporting scope they have within the organisation. This determines, in conjunction with their assigned system role, which reports they have access to.


Direct reports

The user is able to see reports pertaining to themselves and anybody that reports to them directly.

All reports

The user can see reports on everyone that reports to them directly and any users that also report into those people.

Organisation unit

The user can only see reports on users within their organisation unit.


The user can see all users across the organisation, this is the reporting scope that would normally be applied to an administrator.

Organisation (restricted)

The user is able to see all reports within the organisation except for the organisation unit they are placed in – This would be useful for
an HR department, for example, so that they could see their own reports but not the reports of others within the HR department.

Organisation Structure:

There are four columns dedicated to this if it’s required. At this stage it may not be, but, should you wish to use it you can set up the overall organisation and the various levels within it.

The ORGANISATION column requires the overall organisation’s name and the columns LEVEL1_NAME, LEVEL2_NAME and LEVEL3_NAME require the units/levels within it (so LEVEL3_NAME sits within LEVEL2_NAME which sits within LEVEL1_NAME).

Feedback and Knowledge Base