Teams
Overview
Teams in Learn Amp are the primary way to organise users across your platform. They typically mirror your organisation's structure—whether by department, role, location, or project—making it easy to deliver targeted training, assign content, and generate meaningful reports.
Every user belongs to a Primary Team, which determines their manager relationship. Users can also belong to multiple secondary teams, giving you flexibility in how you structure learning and assignments.
Functionality Breakdown
Teams are versatile building blocks for managing learning at scale. Here's what you can do with them:
Assign content – Set Tasks, Learnlists, Channels, Events, and more for team members
Target training – Deliver role-specific or department-specific learning paths
Manage access – Control content visibility based on team membership
Generate reports – Get insights on completion rates, quiz scores, and engagement by team
Create hierarchy – Build nested team structures with parent and sub-teams
Enable collaboration – Social teams offer discussion feeds, dashboards, and member directories
When assigning content to teams, you can choose to:
Assign to primary team members only
Include all sub-teams in the assignment
Target specific teams at any level of your hierarchy
Team Types
Learn Amp offers two types of teams to suit different use cases:
Type | Description | Best For |
|---|---|---|
Standard | Traditional team structure for organising users and delivering learning content | Departments, roles, locations, onboarding cohorts |
Social | Enhanced team with community features including discussion feeds, dashboards, and member tabs | Project teams, communities of practice, interest groups |
Social teams include additional options:
Display a discussion feed for team conversations
Show a team dashboard with key metrics
Enable a members tab for team directory
Allow notes and documents sharing
Privacy Settings
Control who can see and join your teams with three privacy levels:
Privacy | Visibility | Access |
|---|---|---|
Public | Visible to all users | Users can join or leave freely |
Private | Visible to all users | Users must be invited or apply to join |
Secret | Hidden from public view | Users must be invited to join |
Important: Secret teams are only available for Social team types.
Who Can See Secret Teams?
Secret teams have restricted visibility based on user roles:
Owners and Admins – Can see all teams, including secret teams
HR – Can see all non-secret teams, plus secret teams they manage
Learning Designers (with team permissions) – Can see all non-secret teams, plus secret teams they manage
Managers – Can see teams they manage (including secret) and their sub-teams
Learners – Can only see secret teams they are members of
Pre-requisites
To work with Teams effectively, you'll need:
An Admin role with People management permissions
A clear understanding of your organisational structure
Defined manager relationships for team oversight
💡 Tip: Plan your team hierarchy before creating teams. Consider how you'll assign content—by department, role, location, or a combination.
Role Requirements
Action | Permitted Roles |
|---|---|
Create teams | Owner, Admin, HR (with team permissions), Learning Designer (with team permissions) |
Edit teams | Owner, Admin, HR (with team permissions), Learning Designer (with team permissions), Team managers |
Delete teams | Owner, Admin |
View all teams | Owner, Admin, Reporter |
View team chart | Owner, Admin, HR |
Export team data | Owner, Admin |
Manage team members | Owner, Admin, HR, Team managers |
FAQs
Q: What's the difference between a Primary Team and a Secondary Team?
Every user has one Primary Team, which determines their manager relationship and is used for core reporting. Users can belong to multiple secondary teams for additional content assignments and collaboration—for example, a user might be primarily in the Sales team but also a member of a New Starters team.
Q: Can I use my integration to set up team hierarchy on Learn Amp?
Integrations (such as HiBob, BambooHR, or Okta) can automatically create teams and assign users to them based on department or team data. However, parent/sub-team hierarchy relationships are not automatically configured by integrations—you'll need to set these up manually or via CSV import after the teams are created.
Q: Is there a way to filter by the highest group/team?
Yes! When filtering reports or assigning content, you can select any team in your hierarchy. Use the "Assign to all sub-teams" option to include all nested teams beneath your selection. The Teams Chart view provides a visual representation of your complete hierarchy to help you identify top-level teams.
Q: Who can see secret teams?
Secret teams are hidden from general view. Only Owners, Admins, team managers, and team members can see them. HR and Learning Designers (with appropriate permissions) can see secret teams they manage. Regular users will only see a secret team if they're a member of it.
Q: Can a user be in multiple teams?
Yes! While each user has one Primary Team, they can belong to unlimited secondary teams. This is useful for cross-functional projects, interest groups, or temporary training cohorts.
Q: Can a user have different roles in different teams?
Yes. A user could be the manager of one team and a learner in another. Role permissions are evaluated based on the team context.
Q: What happens when I delete a team?
Deleting a team removes all team memberships and unlinks any assigned content. Historical data and reporting are preserved. For large teams, deletion happens asynchronously to avoid disruption.
Q: How do sub-teams inherit content assignments?
When you assign content to a parent team with "Assign to all sub-teams" enabled, all users in the parent team AND all nested sub-teams receive the assignment. If you don't enable this option, only users directly in the selected team receive it.
Troubleshooting
Issue | Solution |
|---|---|
Can't see a team | Check if it's a secret team—you may need to be added as a member or manager. Verify you have the correct role permissions. |
Team not appearing in hierarchy | Ensure the team has a parent team assigned. Check the Teams Chart for a visual overview. |
Users not receiving team assignments | Verify users are members of the team. Check if assignment is set to "primary members only" when you intended to include all members. |
Can't create a team | Confirm you have Owner, Admin, HR (with team permissions), or Learning Designer (with team permissions) role. |
Integration not creating teams | Check integration settings and field mappings. Teams are created from department data—ensure department fields are populated in your HR system. |
Sub-teams not included in assignment | Enable "Assign to all sub-teams" when creating the task or assignment. |
Manager can't see team | Managers can only see teams they directly manage. Check the team's manager assignment. |
Related Articles