Nonprofits experience frequent staff transitions. When a communications manager or development director leaves, organizations frequently discover that domain registrar logins are tied to a former employee's personal Gmail, password records are lost, and outdated content lingers for months without an owner.
A Website Governance Plan establishes clear operational rules, user permission tiers, and editorial workflows to protect institutional memory, maintain security, and ensure long-term website health regardless of staff turnover.
"A website is not an individual's project. It is an enduring organizational asset that requires clear stewardship protocols."
The 4 Tiers of Website Roles & Permissions
1. Executive Owner (Executive Director / Board Chair)
Maintains primary administrative ownership of the domain name registrar (Cloudflare/Namecheap), DNS records, and primary hosting billing account. These credentials must belong to an organizational alias (e.g., admin@yournonprofit.org), never an individual's personal email.
2. Technical Administrator (Lead Developer / IT Partner)
Manages Core updates, security firewalls, daily off-site backups, SSL certificates, and CRM API connections.
3. Content Editors (Communications & Marketing Staff)
Drafts and publishes blog posts, event announcements, and impact stories using locked custom block templates that prevent accidental layout breakages.
4. Program Contributors (Department Leads)
Assigned "Author" or "Contributor" status to submit draft content for editorial review before publishing.
Essential Policies Every Governance Plan Must Include
- Photo Consent & Licensing Protocols: Written documentation that every constituent photo has a signed media release form on file.
- Offboarding Checklist: Immediate password reset and 2FA revocation within 24 hours of any staff or contractor departure.
- Quarterly Content Audit: A scheduled review to prune expired event pages, update staff rosters, and refresh outdated statistics.
Need a website governance plan for your team?
I help nonprofits create clear editorial workflows, role permissions, and maintenance plans.
Build a Governance Framework