Skip to content
All documentation

Teams & Delegated Leads

Group members into named teams, assign leads, and scope courses to a single team so team-specific content reaches only that team's learners.

What it is

Teams are org-scoped groups of members. Each team has members and one or more leads. A lead is a member delegated to author and publish courses for that team only, without gaining access to the wider org console.

A course can be scoped to a single team. An org-wide course (no team) is visible to everyone; a team-scoped course merges into the learning path only for members of that team. Admins and owners see every course regardless of team.

Use

  • Create a team in Admin → Teams: give it a name and optional description, then add members from your organization and mark one or more as leads.
  • Pin a course to a team from the course editor's Team picker (default is org-wide, visible to everyone).
  • A lead signs in and authors courses under Admin → Courses; they see and manage only courses scoped to teams they lead. They cannot create org-wide courses, open another team's course, or manage team membership.
  • A learner sees a team-scoped course in their path only when they belong to that team; org-wide courses always appear.

Setup

Admins and owners manage teams under Admin → Teams: create, rename, and delete teams, add or remove members, and promote or demote leads. Team management is admin-only; a lead cannot manage teams or assign leads.

Assign a course to a team from its editor. No extra configuration is required for team visibility; membership resolves automatically at read time.

Security

  • Every team, membership, and course is org-scoped, and cross-org access is blocked at the schema level with composite foreign keys tying teams, memberships, and courses to their org.
  • A lead's authorization is checked against their membership role on every request; a lead can never create org-wide content, read another team's content, or re-scope a course outside the teams they lead.
  • Adding a member verifies the user belongs to the same org before insert, so a member from another org can never be added to a team.
  • Deleting a team removes its memberships and its team-scoped courses (they die with their scope rather than widening to org-wide).