Teams

Teams describe the working structure of an organization: departments, groups, divisions, or project squads, which then make it convenient to view results. It is not a separate permission system or a task tracker. A team is needed so that members can find their place, and analytics can show not only the overall picture but also differences between parts of the organization.

How the tree is structured

On the teams page, the organization is the root of the tree. Under it are first-level teams, and they can have direct subteams. Depth is limited to two team levels: organization → team → subteam. This is enough for practical navigation and doesn't turn the structure into a cumbersome org chart.

A team card shows the name, a visual marker, and the number of members. From the tree, you can go to a specific team's card: there you can see its members, subteams, and available surveys. Management actions for a team are not hidden in the tree — they are performed in the team card.

Team membership

An employee belongs to only one team within the organization. If a person is already in a team, they cannot join a second one. This keeps team analytics clear: a single participant's response is not spread across multiple breakdowns.

Members of different roles, including anonymous guests, can join or leave a team. In an anonymous organization, such a participant remains under a pseudonym. Team membership helps accurately collect the team breakdown, but does not reveal raw answers: raw answers are not shown to anyone.

Who manages teams

The organization owner and users with the Admin role can create, edit, and delete teams. Other roles see the tree, open team cards, join a suitable team, and go to results, but do not change the organization structure.

A team has an owner, name, color, and icon. If a team is created in the wrong branch, the parent of an already existing team is not changed: it is deleted and recreated in the right place. When a team is deleted, its subteams are also deleted, so the structure should be edited thoughtfully.

How teams affect results

Teams become an analytical breakdown. After summarizing the results, the platform can show how a specific team responded to the survey: overall score, dynamics, categories, and a brief summary. This helps identify where the tension is company-wide and where it is concentrated in a specific group.

The team breakdown is especially important for the Ask → See → Discuss → Verify cycle. If one team underperformed on a topic, and another handles it calmly, the solution should be sought closer to the point of tension. This way, changes stay targeted and don't turn into a blanket reform for everyone.

At the same time, privacy is maintained. Team results and summaries are shown only where there is enough data for safe display. If there are few responses, the platform hides the breakdown or shows a placeholder so that no one can guess the respondent's identity from the results.