Teams and assignment

Teams are the delivery mechanism in Vidext: you assign courses to teams, and team members are enrolled automatically. Get the team structure right and distribution stops being work.

Vidext — Teams

Creating teams

Anyone with the team-creation permission (organization admins by default) can create teams from Settings → Teams. A team needs little: a name and the people in it. Members are added from your organization's existing members; adding someone to a team requires that they are already an active member of the organization.

From a published module to something people can open

Publishing a module does not deliver it. Modules live in your library; learners are assigned courses. Between the two sits the whole of distribution, and it is four deliberate actions in Content → Courses:

Skip the last one and everything looks correct from the admin side while reaching nobody. See Draft and published for how the same explicit-decision rule governs modules.

Vidext — Courses

Assigning a course

Assign a released course to one or more teams. The moment you do:

• every current team member is enrolled in the course's modules;
• each newly enrolled learner receives an enrollment email;
• anyone who joins the team later is enrolled automatically in what the team already has.

Unassigning works in reverse. There is no per-learner enrollment management to maintain.

Structuring teams well

Model teams around who learns what, not the org chart:

• Audience teams ("Support — EMEA", "New hires Q3") map cleanly to course assignments.
• One person, many teams is normal — people accumulate the union of their teams' assignments.
• A team per location or function only helps if those groups genuinely train differently.

Team roles

Within a team, people are admins (manage the team) or learners (receive assigned courses). Module authoring is authorized by the organization role, not the team role. See Roles and permissions.