Reporting teams

Organization and its branches

Every installation has a built-in Organization team. Named teams sit beneath it, directly or through other teams. People without a named direct team appear at Organization.

For example, Organization might contain Sales and Support, with Enterprise beneath Sales. A person belongs directly to Enterprise and appears in the Sales reporting branch through that hierarchy. They do not need two direct team memberships.

Organization cannot be renamed, moved, or deleted. An administrator can assign its manager; that responsibility covers everyone across the hierarchy.

Create a team and assign its manager

Administrators open Account menu → Manage organization → Teams.

1. Select Add team, or open an existing team's actions and select Create subteam.
2. Enter a unique Team name and choose its Parent team. Select Organization for a team directly beneath the root.
3. Choose a Manager, or leave No manager. Eligible people are active Managers, Contributors, or Administrators.
4. Select Save team, or Review changes when reporting or learning changes need review. Inspect the affected people and save the reviewed change.

The Manager role alone gives no reporting branch. If an intended manager is a Learner, change their Access role in People before selecting them. A preregistered manager can be chosen, but must activate their account through verified sign-in before using reports.

The manager sees this team and all its subteams regardless of their own team membership. Selecting a manager does not move them into the team. A Contributor can therefore publish content and separately report on an assigned branch. See Roles and permissions.

To change responsibility later, open the team and select Edit team details. On the Organization page, use Edit manager.

Add or move members

Open the team's Members view and select Add members. Choose people, select Review changes, and review the reporting and learning effects before confirming Add members.

Adding someone who already belongs directly to another team moves them to this team. Their account and saved progress remain. Members of subteams appear in the branch for reporting, but their direct membership is still in their own team.

For direct members, row or selection actions offer Move to team and Remove from team. Removal returns the person to Organization. People already at Organization must be moved into a named team rather than removed from the organization.

You can also set a person's Reporting team from People or update several people through Import people and teams.

Use teams as learning audiences

Select a team directly when assigning a course, curriculum, or relevant update. Team audiences include their descendant teams. Organization reaches everyone in the roster, including people without a named team and future members.

If a learning audience needs several branches or selected individuals, link teams into a Learning group. A learning group adds no reporting authority. Neither a team nor a group restricts access to published content.

Course assignments explains the audience picker and what happens when memberships overlap. Progress and reporting explains the manager's My team's progress view.

Move a branch

Use Move team in the team's actions, or Move selected teams after Select multiple. Choose the destination and review the move before saving. Selecting a parent and one of its descendants together is not allowed, and a team cannot move beneath itself or its descendants.

A moved team keeps its direct members, subteams, and its own learning-group links. Its new position changes ancestor managers' reporting scope and can change learning inherited from ancestor teams or linked branches. Review these changes even when the people inside the moved branch stay together. Saved course completion remains.

Delete a team

Before deleting a team, remove its directly assigned learning and its links to learning groups, saving those changes first. Organization cannot be deleted.

Select Delete team, or Delete selected teams for a batch, and review the affected records. Confirm Delete teams only when the result is intended:

• Direct members of deleted teams move to Organization, not to the deleted team's former parent.
• Surviving immediate subteams move to Organization, retaining their own members and nested branches.
• Accounts and saved learning history remain. Reporting scope and learning coverage can change.

Team deletion has no 30-day restore flow. If the purpose is a reorganization, moving a branch usually preserves more of its existing structure.