Adding a team

1. Click the Teams menu item
2. Click "New team"
3. [Optional] Choose a parent team (see notes blow about Team Hierarchies) .
4. Give the team a name
5. Configure how this team will be supervised (see Configuring Supervisors)
6. [Optional] Define skill categories that will be associated with this team. Any people inheriting their skill set from this team will inherit these skill categories for use in their next skills assessment.

Placing people into teams

If the person already exists in the system:

1. Click the Teams menu item
2. Make sure the "Show people" checkbox is ticked
3. Drag and drop the person into the desired team.

If the person does not yet exist in the system, and you wish to have them join by invitation:

1. Make sure you have some teams set up in the system
2. Click the People menu item
3. Click "Add people"
4. Click "Yes" when prompted if you would like them to be able to log in.
5. Click "Add people by invitation"
6. Enter the email address(es) and click "Send invitations"
7. Select desired team for each person from the drop down menus.

If the person does not yet exist in the system, and you wish to add them manually:

1. Click the People menu item
2. Click "Add people"
3. If you want this person to be able to log in click "Yes" when prompted, followed by "Manually add a person", otherwise click "No".
4. Fill in the details for the person and select a team
5. Click save

If the person does not yet exist in the system, and you are using Single Sign On:

1. Go to Admin -> Settings -> Single Sign On
2. Locate the "Default team" option and select the desired team to apply for all people created via Single Sign On.

Team Hierarchies

Team hierarchies allow you to define parent-child relationships between your teams. There are four main functions that team hierarchies provide:

1. Data aggregation. When you view a parent team, data from all sub-teams will be included (eg: on team dashboards, and in the heat matrix)
2. Skill inheritance. Sub-teams will inherit skill categories from parent teams. That is, any skill categories assigned to parent teams will automatically be assigned to any/all sub-teams. See "How skill category inheritance works" below for more information.
3. Permission inheritance. If a person is granted permissions for a parent team, all of those permissions will automatically apply to all of the sub-teams. For example, if a person is granted supervisor permissions for a parent team, they'll also be a supervisor of all sub-teams.
4. Logical grouping and structure. Team Hierarchies provide the ability to replicate your internal organization structure in Skills Base so that people are grouped and arranged in a way that is familiar to employees.

Setting up team hierarchies is easy; simply select a parent team from the drop down box when adding or editing a team, or drag and drop teams directly into one another on the Team Directory page.

How skill category inheritance works

A team will always inherit skill categories from all of its parent teams. However, please note the following:

• All inherited skill categories are saved directly against a child team when the child team is saved via the Team Edit/Add page.
• Therefore, if that child team is later moved to a different parent it will continue to take with it all of the skill categories from all previous parent teams.
• Inherited skill categories are not saved directly against a child team when the child team is moved via the Team Directory Tree, however the categories will still be inherited. The reason for not saving inherited categories is that it is not obvious to administrators that moving a team in the tree could result in changes to the team's skill categories and so the system will not make the changes unless an administrator explicitly saves the categories via the Team Edit or Add pages.

The decision to save all skill categories against a team was taken so that administrators have full control to define the skill category list for each team in the event a team needs to be moved. Otherwise, administrators would only have the ability to define the differences between a team and it's parents, and those differences become irrelevant when the team is moved to a different parent.