Become a sponsoring admin

Sponsorship is a real, public commitment — not a casual claim. Verified admins are publicly on the hook for the charity they steward, which creates both accountability and recognition.

What sponsorship is

A sponsoring admin accepts public responsibility for stewarding one FFC charity site through its build and ongoing maintenance. Sponsorship is the gating mechanism for provisioning: a site cannot move from needs a sponsoring admin to active build without an assigned, verified sponsor.

Prerequisites

  1. Complete the FFC Microsoft 365 Global Admin training (see the training plan).
  2. Have a verification conversation with FFC (text 520-222-8104).
  3. Be added to the sponsoring-admins GitHub team in the FreeForCharity org — team membership is the verification artifact.
  4. Be granted access to the private coordination repo for admin coordination.

How to claim a site

Browse the “Needs a sponsoring admin” queue, comment on the issue for the charity you want to sponsor, and FFC assigns you. An automated check confirms your sponsoring-admins membership before any provisioning is triggered — accidental assignments are reverted automatically.

Capacity & stepping back

We recommend a maximum of 3 concurrent active sponsorships (one in active build, others in maintenance). You can step back any time by commenting on your assigned issue and requesting reassignment — the site returns to the pool. This is normal; admins should never feel locked in.

The commitment

By accepting assignment as a sponsoring admin for an FFC charity site, I commit to:

  • Actively coordinating with the charity through the build phase — responding within 3 business days during active build and within 7 business days during ongoing maintenance.
  • Maintaining the site post-launch, including security updates, link-rot fixes, and content updates the charity requests.
  • Escalating to FFC central via the public escalation channel or the private coordination repo when issues exceed my scope or judgment.
  • Operating within FFC’s prioritization policy and code of conduct.
  • Not soliciting the charity’s contacts for unrelated commercial purposes.
  • Treating information shared in the coordination repo as confidential to the FFC community.
  • Requesting reassignment promptly if circumstances change rather than going silent.
  • Maintaining no more than 3 concurrent active sponsorships unless explicitly approved by FFC leadership.

What gets escalated

DNS, infrastructure, scope, and policy questions are handled publicly in this repo. Security, abuse, charity disputes, and anything sensitive go to the private coordination repo or directly to FFC central — never in a public issue. See Submit a request for the escalation paths.