Skip to content

Teams

At a glance

Teams let a group of Citizen Science users work on a shared set of deployments. Users create and join teams in the Citizen Science frontend; admins oversee them in the Expert admin.

  • Time: a few minutes per team
  • Who: team leaders (any user) in the CS frontend; superusers in the Expert admin

What a Team is

A Team groups users at global level — it isn't owned by a project:

  • Each team has one Team Leader (its creator/owner — the only user who can edit or delete it) and any number of Members.
  • Membership goes through an invitation flow: the leader invites a user, who approves or rejects; a membership is Pending until then. Members can leave on their own.
  • A team can optionally carry a polygon (a geographic area of interest).
  • Within a Classification project, a team can be granted a set of deployments to work on (a Team classification project deployment row) — that's how a leader splits a project's cameras between groups of volunteers. The same team can have different deployment sets in different projects.

Managing teams as a user (CS frontend)

Team management lives in the Citizen Science frontend, inside a project's pages:

  1. Create a team (name + description) — you become its Team Leader.
  2. Search for users and invite them; invitees see the invitation and approve/reject it.
  3. As leader, share deployments with the team inside the current classification project — members then classify resources from those deployments.

Overseeing teams as an admin (Expert admin)

Three changelists cover everything the CS frontend creates:

Changelist What's there
Teams → Teams Name, description, leader, members, optional polygon (editable on a map widget).
Teams → Team memberships Per-user rows with Role (Team Leader / Member) and Status (Pending / Approved / Rejected) — fix a stuck invitation here.
Teams → Team classification project deployments Which deployments each team works on, per classification project.

GDPR masking removes memberships

The Mask selected Users admin action deletes the user's team memberships along with other personal links — a masked user silently disappears from their teams.

REST API

The CS frontend drives teams through REST endpoints mounted at /teams/ — team listing and creation, member search/invite/approve/reject/leave, and per-project deployment sharing. See the API reference for the live schema.

See also

  • Users & roles — project roles and account administration (teams are separate from project roles)
  • Roles & access model — how teams fit into the overall permission model