Load your org structure

An org structure is the list of teams in a workspace, how they nest (company, department, team, to any depth), who leads each one, and who belongs to it. Surveys use it to report results by team: see Team reports.

Each workspace has one org structure. If you run surveys for several client organisations, use one workspace per client.

Org structures are part of team reports, available on the Growth plan and above. Workspace owners and admins can load one; they also need permission to import contacts, because the people in the file become contacts.

Prepare the file

Use a CSV file saved as UTF-8, with one row per employee and these columns:

Column	Required	What it holds
Employee email	Yes, on rows that are people	The person’s work email
Team code	Yes, on every row	Your own ID for the team, up to 64 characters. Re-importing with the same codes updates teams instead of creating new ones
Team name	Once per team	The name leaders and reports show
Parent code	For teams inside another team	The code of the team above it
Leader email	Optional	Who receives the team’s report. Several leaders go in one cell, separated by ; or ,
First name, Last name	Optional	Added to the contact

A row with a team code and no email defines a team with nobody directly in it, such as a department that only contains other teams. A team’s name, parent and leaders can be on any of its rows. Commas, semicolons and tabs all work as separators.

Download a template from Workspace Settings → Org Structure → Download a template.

Check and import

1. Go to Workspace Settings → Org Structure.
2. Choose your file and select Check file. Nothing is saved yet.
3. Read the result. It lists how many teams are new, updated and to be archived, and how many people the file holds.
4. Select Import.

Check file refuses a file that has any of these problems, and lists each one with its row number:

• a row without a team code, or an email address that is not valid;
• a team given two different names or two different parents;
• a parent code that is not in the file;
• teams that are each other’s parents;
• a person listed in two teams. Each person belongs to one team.

It also warns, without refusing, about teams with no leader email (nobody can be sent their report) and teams with fewer than 5 people, counting the teams under them. A team below the minimum gets no report of its own, but its answers still count in the team above it and in the company.

The file is the whole structure

Each import replaces the structure:

• Teams in the file are created or updated by their code.
• Teams that are not in the file are archived. Surveys already sent keep reporting on them.
• People in the file are added to your contacts, or updated if they are already there, with their team. Unsubscribed and suppressed addresses are skipped, and your plan’s contact limit applies.
• People who had a team but are not in the file are taken off it. They stay in your contacts.

A person’s team is stored in a contact field called Org unit, which holds the team code.

After a reorganisation

Load the new file. Each survey keeps its own copy of the structure, taken when it started reporting by team, so earlier surveys still report on the teams they were sent to. To bring a survey that has not been sent yet up to date, open its settings and select Refresh from org structure.

If most of the team codes in the new file are ones the workspace hasn’t had before, the check step warns you before anything is saved. If the teams were only renumbered, keep their old codes so each team still matches its earlier results. If they really were split or merged, map the new teams to the earlier ones in the team reports: see Teams that were reorganised.