Google Workspace Admin Training

Run accounts, groups, and security for charities on Google

The administrator path for charities that run on Google: own accounts, groups, shared drives, sharing, and security in the Admin console β€” backed by the Google Workspace Administrator certification. Used to be folded into general admin work; now a first-class role.

Administrator level β€” backed by Google Workspace Administrator
Administrator level. Full administrator depth, owned org-wide, backed by certification. You hold the Google Admin console for the charities FFC supports β€” work through what you own below, and lean on your AI assistant to explain anything new before you change it.

What you're responsible for

Google Workspace

Administrator

Accounts, groups, and sharing for charities that run on Google.

Your goal: Administer Google Workspace end to end, backed by certification.

  • Configure security: 2SV enforcement, context-aware access, and admin-role delegation; review the security dashboard and alert center. (Security best practices)
  • Own domain and email routing (MX, SPF, DKIM, DMARC), data regions, and retention/Vault policy for the tenant.
  • Work toward the Google Workspace Administrator certification. (Workspace Administrator cert)

Accounts & Access

Practitioner

The logins that prove the website and email are yours.

Your goal: Manage your own credentials and collaborate on shared repositories.

  • Set up a professional GitHub profile and a profile README managed "as code". (Introduction to GitHub)
  • Understand repository roles (read / triage / write / maintain) and request the least access you need.

Security & Trust

Practitioner

Keeping your site and accounts safe.

Your goal: Triage repository security and keep the supply chain healthy.

  • Enable and triage Dependabot and CodeQL alerts; review PR checks before merge. (Securing your repository)
  • Keep dependencies current and understand what each CI check verifies.

Building with AI

Operator

The one skill that powers everything above.

Your goal: Describe what you want, review it, and approve β€” let the agent do the work.

  • Describe changes in plain English; the assistant figures out the technical steps.
  • Always read the summary of what changed before you approve.
  • When you’re unsure or something looks wrong, ask the assistant to explain β€” or escalate to FFC. (Site Owner walkthrough)

Governance & Privacy

Operator

Staying compliant, accessible, and trustworthy.

Your goal: Keep required policies current and publish responsibly.

  • Your site has a privacy policy and cookie notice. Keep them accurate when what you collect changes β€” ask your assistant to update them.
  • Accessibility matters: ask your assistant to add descriptive alt text to images and keep color contrast readable.
  • Remember your site is public. Only post board minutes or documents your board approved for public release. (Board minutes caveat)

Domains & DNS

Operator

Your web address β€” and the email that depends on it.

Your goal: Understand your domain and keep it healthy, without breaking anything.

  • Know your domain name and that it must be renewed (usually yearly). Confirm who renews it β€” FFC or your charity β€” so it never lapses.
  • Understand at a high level that DNS records point your web address at your site and route your charity email. Your site is mapped through Cloudflare to GitHub Pages.
  • Don’t edit DNS records yourself. If something needs changing, ask your AI assistant to explain it and have an FFC admin make the change.
  • Red flag: if your site won’t load or email suddenly stops, suspect DNS or an expired domain and escalate to FFC right away.

Where to next