Manage Teams

How to create, structure, and manage teams in Teams Directory.

Manage Teams

This section explains how to create, structure, and manage teams in KnowCount. Teams are a foundational element of your organization’s setup and are required for assigning people, configuring permissions, and linking skill categories.

1. What Teams Are Used For

In KnowCount, Teams are mandatory and serve multiple key functions:

  • Control permissions — Supervisors and access rights are defined based on team membership.
  • Mirror your organizational structure — Teams allow you to group people logically.
  • Assign skill categories via Skill Sets — Skill categories can be attached to teams, making assessments easier to manage and maintain.

Each person can belong to only one team at a time, but team membership can change over time to reflect organizational changes. People can be assigned to multiple projects (handled separately), but only one team.

2. Adding a Team

To create a new team:

  1. Click the Teams menu item from the left-hand navigation.
  2. Click the New team button.
  3. [Optional] Select a Parent team from the dropdown if you want to create a hierarchy (see section 4 below).
  4. Enter a Team Name (required).
  5. Configure Supervision by selecting or assigning a Supervisor:
    • Supervisors are defined by their Security Group with the People > Assess privilege.
    • Scope options:
      • Everyone: can assess anyone in the organization.
      • Team members: can assess only members of their team and subteams.
  6. [Optional] Assign Skill Categories to the team. These will be inherited by all people whose skill sets are tied to the team.
  7. Click Save.

🛈 Skill Categories define what people on the team will be assessed on. These should reflect skill domains, not organizational roles.

3. Placing People into Teams

You can assign people to teams in three ways depending on whether they already exist in the system.

A. If the person already exists

  1. Click the Teams menu item.
  2. Ensure the Show people checkbox is checked.
  3. Drag and drop the person into the desired team in the Team Directory Tree.

B. If the person does not exist and should be invited

  1. Make sure at least one team has been created.
  2. Click the People menu item.
  3. Click Add people.
  4. When prompted about login access, click Yes.
  5. Click Add people by invitation.
  6. Enter one or more email addresses and click Send invitations.
  7. Use the dropdown to assign each invited person to the appropriate team.

C. If the person does not exist and should be added manually

  1. Click the People menu item.
  2. Click Add people.
  3. When prompted about login access:
    • Click Yes, then select Manually add a person if login is required.
    • Click No to add them without login access.
  4. Fill in the person’s details and select their team from the dropdown.
  5. Click Save.

4. Team Hierarchies

Team hierarchies allow you to nest teams under parent teams. This structure is useful for:

  • Data aggregation — Parent teams can view combined data from all subteams in dashboards and reports.
  • Skill inheritance — Skill categories assigned to a parent are automatically inherited by its subteams.
  • Permission inheritance — Supervisors of parent teams automatically gain assessment rights over all subteams.
  • Organizational modeling — Team hierarchies can replicate your company’s structure for intuitive navigation and reporting.

Setting up a hierarchy

You can define team hierarchies in two ways:

  1. When creating/editing a team, select a Parent team from the dropdown.
  2. On the Team Directory Tree, use drag-and-drop to nest teams under one another.

How Skill Category Inheritance Works

Skill categories assigned to parent teams are inherited by all child teams. Inheritance depends on how the team is created or moved:

  • Via the Team Edit/Add page:
    • Inherited categories are saved directly on the child team.
    • If the team is later moved to a new parent, it retains the original inherited categories.
  • Via drag-and-drop in the Team Directory Tree:
    • Inherited categories are not saved directly.
    • The new parent’s categories are inherited implicitly, without overwriting existing ones.

🛈 This design gives administrators full control over a team’s skill profile and prevents unexpected changes when teams are reorganized.

Getting started