teams-safeguarding

Enforce private-by-default photo visibility with teacher approval for school teams.

132|42|Updated Aug 19, 2020
One-click install
npx skills add https://github.com/OpenLitterMap/openlittermap-web --skill teams-safeguarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teams-safeguarding
Source: https://github.com/OpenLitterMap/openlittermap-web/tree/main/.ai/skills/teams-safeguarding
Command: npx skills add https://github.com/OpenLitterMap/openlittermap-web --skill teams-safeguarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

School teams require a privacy-first workflow to protect students in photos and ensure data quality through teacher approvals.

Core Features & Use Cases

  • Automatic privacy: PhotoObserver automatically sets is_public = false for photos uploaded to school teams.
  • Teacher approval flow: photos must be reviewed and approved by a teacher before becoming public.
  • Masking of identities: MasksStudentIdentity hides student names as "Student N" to protect privacy.
  • Participant management: facilitator queue, participant slots, and token-based workspace enable controlled collaboration.
  • Private broadcasts and access controls: private team data and private channels prevent public leakage and admin overlap.
  • Safeguarding invariants: school teams always enforce non-trusted status and safeguarding settings.

Quick Start

Set up a school team workflow with private-by-default photos and teacher approvals to protect student identities.

Frequently Asked Questions about teams-safeguarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep school team photos private until teacher approval?

School team photos are kept private by automatically setting visibility to false upon upload, requiring teacher approval before any photo becomes public to safeguard student identities.

How does privacy masking work for student identities in school teams?

Privacy masking hides student names by automatically replacing them with generic identifiers like "Student N" before photos enter the teacher review queue, ensuring names are not exposed during the approval workflow.

Can I use a facilitator queue workflow for school photo approvals?

Yes, you can use a facilitator queue workflow that provides participant slots and token-based workspaces to enable controlled collaboration and atomic photo approvals for school teams.

Does this safeguarding workflow affect community teams?

No, community teams remain completely unaffected by the safeguarding workflow, which only enforces private-by-default photo visibility, identity masking, and non-trusted status for school teams.

What are the limitations of private broadcasting for school team photos?

Private broadcasting limitations include strict role-based access controls and private channels that prevent public leakage and admin overlap, ensuring approved school team photos remain isolated within authorized participants.