20.1.9. Teams

Teams let you bundle several auditors (or units) together so they compete as a single participant. Every observation made by any team member counts toward the team’s score.

20.1.9.1. Why use teams

Standard scopes make one participant per facility / unit / auditor / HCP type. Teams add a fifth scope that isn’t derived from the data model:

• “Day Shift Auditors vs. Night Shift Auditors – first team to 500 observations wins.”

• “Surgical Floor combined (ICU + Step-Down + OR) vs. Medical Floor combined.”

• “Green Team and Blue Team hospital-wide competition.”

Teams are persistent. They don’t have to be recreated per challenge – once defined, any challenge can target them by setting scope = Team (code 4).

20.1.9.2. Creating a team

Use the /challenges/teams endpoint or the Teams page.

• Name (required) – shown everywhere the team appears.

• Description – optional notes about the team’s composition.

• Corporation – defaults to the current corporation. System-level admins can create teams scoped to any corporation.

• Active – Inactive teams are hidden from challenge-scope pickers but preserved so their past challenge history remains intact.

20.1.9.3. Roster (members)

Each team has a roster of members in challenge_team_members. A member is identified by:

• memberparticipanttype – usually 2 (Auditor) but 1 (Unit) is also supported.

• memberparticipantid – the user UID or unit ID.

A single user can belong to multiple teams. The uniq_member index prevents the same user from being added twice to the same team.

When a team challenge is computed, the scoring query unions all members’ observations:

AND s.observerid IN (
  SELECT memberparticipantid
  FROM challenge_team_members
  WHERE teamid = <team>
    AND memberparticipanttype = 2
)

20.1.9.4. Using a team in a challenge

In the Challenge Detail (Editor) editor:

1. Set Scope = Team.

2. Leave Scope ID = All to compete every active team against each other, or set it to a specific team ID to score that one team in isolation.

The rest of the challenge (metric, threshold, dates, reward) works exactly as for any other scope.

20.1.9.5. Team rewards

When a team wins:

• Points are posted to the team as the participant (participanttype = 4, participantid = <teamid>), not to individual members. This keeps the ledger clean for the case “the team earned X” without needing to divide by members.

• The badge is granted to the team similarly.

• Email notifications are not sent for team wins by default (there is no “team email”). Clients who want per-member notifications on team wins can add a post-close hook.

To see a team’s running balance, use the Participant Profile page with participanttype=4&participantid=<teamid>.

20.1.9.6. Deactivating a team

Set Active to off or use the DELETE endpoint (which performs a soft delete: active = 0). All past awards survive. Reactivating restores the team immediately; the roster is preserved.