
Essay Tech Governance
Password and Credential Management Policies for Nonprofits
A risk-ranked, owner-assigned plan for protecting nonprofit accounts.
A password and credential management policy for nonprofits should be built around shared accounts, staff turnover, aging software, and limited IT support. The workable approach is to rank accounts by risk, provide tools that enforce the rules, and assign responsibility for removing access. For nonprofits with custom software, that responsibility also extends to reviewing authentication and application secrets before users arrive.
Why nonprofits are structurally different from the organizations most credential guidance is written for
Nonprofits often split the technical work among people whose main jobs are running programs, managing operations, or serving on the board. A policy that assumes an IT department starts from the wrong premise. Someone must still set up accounts, manage access, and respond when a volunteer leaves, but that work competes with the mission.
Shared logins illustrate the mismatch. Per-seat pricing can make individual accounts unaffordable, so staff share access to keep work moving. Volunteer cycles then change who needs those credentials faster than a manual process can reliably track. Meanwhile, software given to the nonprofit and systems left behind when grants end may support only legacy authentication. An executive director cannot make those systems support modern controls by approving a stricter document. Without funding, compatible tools, and a named owner, the document becomes an unfunded mandate.
What attackers actually want from a nonprofit, and why credentials are the entry point
A nonprofit’s mission does not make its data less valuable. Attackers have a reason to break in to get donor payment details, sensitive client records, and financial accounts tied to grants.
Credentials offer a cheap route into those assets. With stolen or reused passwords, attackers can get into donor portals, volunteer systems, and payment platforms without a complex attack. A shared login widens the blast radius because an attacker can reach everything that account touches, while the organization cannot reliably distinguish the actions of its legitimate users. Phishing adds another route when staff mix personal and organizational email and have no clear way to report suspicious messages.
The Louvre’s surveillance server password, “LOUVRE”, illustrates how basic a credential weakness can be. For a nonprofit, the useful question is therefore not whether its mission attracts attention, but what a single compromised account would let someone reach.
What the current governing standard actually requires, and how it differs from what most nonprofits have on paper
NIST finalized SP 800-63B-4 on July 31, 2025, establishing a password baseline that rejects several familiar burdens. Its length-first approach sets a higher minimum when a password is the sole authenticator and allows a shorter minimum when it is used with MFA. It rejects mandatory mixtures of uppercase letters, numbers, and symbols. It also requires checking new or changed passwords against known-compromised credentials and allowing paste in password fields so password managers can work.
NIST rejects routine rotation in favor of changes when there is evidence of compromise. For an under-resourced team, that removes a recurring administrative chore without abandoning protection. The replacement, however, needs someone or something watching for compromise.
Complexity rules invite predictable, weak passwords such as “Summer2026! Longer passphrases offer a more useful direction than punctuation requirements. The good news is that modernization can mean fewer demands on memory and a steady workload for staff.
Why awareness training alone has not reduced credential breaches, and what the control model needs to change
Security training can explain why password reuse is dangerous, but it cannot make an unsupported system enforce better rules. Nor can it revoke a departing volunteer’s accounts. Training changes intent without necessarily changing the conditions in which people act. If secure behavior remains optional or difficult, awareness alone cannot make it dependable.
This is a governance failure. The controlling questions concern who can create accounts, which standards apply at creation, how access ends, and what happens after compromise. Those decisions need to be part of how the organization runs. They cannot be delegated to individual vigilance.
Consider a nonprofit with thirty staff, rotating volunteers, and a growing collection of SaaS tools. Spreadsheets and quarterly reminders work only if someone knows about every change and takes the right steps. As complexity rises, that dependency becomes harder to sustain. The structural response is to connect credential controls to the identity lifecycle, so a departure triggers access removal automatically where the systems support it. Training should explain and support the controls.
The four nonprofit-specific failure modes a credential policy must address directly
Shared accounts prevent reliable attribution and make individual access difficult to withdraw. Removing one person may mean changing the credential for everyone. Yet a ban without an affordable alternative leaves the original pricing problem untouched. The policy response is to identify nonprofit or free tiers with individual accounts and prioritize single sign-on, or SSO, across tools.
High turnover and volunteer cycling leave people with access after they leave the team when offboarding relies on a separate security checklist. A departure is an operational event with a security consequence. The policy response is a written offboarding protocol tied directly to HR events and volunteer departures.
Aging systems and legacy software create gaps that modern password rules cannot close. Some cannot support MFA or current authentication requirements. An unpatched system can also provide an entry point for movement toward more sensitive data. The policy response is a tiered inventory that identifies unsupported controls, marks affected systems as elevated risk, and prioritizes replacement or isolation.
No dedicated IT person means enforcement can remain everybody’s concern and nobody’s responsibility. Audits slip, MFA enrollment stalls, and password manager rollouts remain unfinished. Ownership cannot be left implicit. The policy response is to name a credential governance owner, even part-time, and choose tools that display compliance status without a manual audit.
Per-seat pricing can make individual accounts unaffordable, so staff share access to keep work moving.
Building a credential policy around nonprofit reality rather than enterprise compliance templates
For a team facing these constraints, the practical starting point is a tiered credential inventory. Put financial accounts, donor CRM, payment processors, and email administration in Tier 1, requiring individual accounts, MFA, and a password manager. Put the tools used to run the nonprofit that hold staff data in Tier 2, with individual accounts and MFA. Use Tier 3 for shared social media and low-sensitivity tools, with credentials kept in a vault and checked quarterly. Risk sets the order of work.
Make the password manager required infrastructure. Unique passwords are difficult to sustain if staff must remember them all. For Tier 3 accounts, use the vault as the system of record and restrict access to a named role. Some weaknesses of a shared account remain even with these limits in place.
Prioritize executives and finance teams during MFA rollout because of their exposure to business email compromise. Google Workspace and Microsoft 365 support enforcement at the admin level. Phishing-resistant options, including passkeys and FIDO2 hardware keys, offer the strongest protection. SMS codes are an interim step up from no MFA.
Write offboarding into the credential policy itself. Specify the responsible person, systems to check, maximum time to revoke access, and how completed revocation will be verified. Apply a lightweight version to volunteers too. Replace scheduled password changes with event-triggered changes for suspected compromise and affected shared credentials after departures or role changes that remove access need. Review access quarterly, starting with Tier 1. For a small nonprofit, covering three to five critical systems is an achievable scope.
How the choice of tools shapes what credential policy is actually enforceable
A platform’s affordable tier determines which rules a nonprofit can enforce. At that price, does it have individual accounts, MFA enforcement, role-based access control, and SSO? If not, the policy inherits manual work. Free software can still cost a lot to run.
Baserow’s free open-source edition has neither SSO nor role-based permissions. Role-based permissions begin on Advanced, while SSO begins on Enterprise. NocoDB’s free self-hosted community edition has basic roles but no SSO. Its SSO starts on Plus, audit logs on Scale, and SCIM provisioning on Enterprise. When the nonprofit runs these free editions itself, it must handle backups, patching, and access revocation without the identity controls that come with higher tiers.
Salesforce Nonprofit Cloud shows a different level of access control that can be enforced, though it is not a recommendation for every nonprofit. It offers role-based access, field-level security, audit trails, and login IP restrictions, with 10 free licenses for qualifying nonprofits through the Power of Us program. Those controls provide options that shared spreadsheets and consumer databases may not. SeaTable is also relevant to organizations with location-specific donor data obligations because of where it is based, where its servers are located, and its self-hosting option. Where a system is based, however, says nothing about which authentication it supports.
TechSoup is a procurement channel for discounted and donated software, including products from Microsoft, Adobe, and Cisco. Azure Key Vault can hold application secrets, encryption keys, and certificates. These resources address different needs. The selection question remains whether the available product and tier can enforce the organization’s actual policy.
The credential risks that come with software built on AI tools or by freelancers, and how to address them before users arrive
Custom software moves part of credential risk into the codebase. An application assembled with AI tools or through a freelancer engagement may work while retaining tokens with no expiry, sessions that survive logout, or unsuitable password hashing. A staff password policy cannot fix those defects. A working MVP is not proof of safe authentication.
Before bringing in an outside development team, a nonprofit’s technical debt assessment should cover authentication and session handling, authorization on every endpoint touching donor or client data, secrets management, and dependency scanning for known vulnerabilities. An example deliverable for a request to “check security” is a scored register covering those concrete review dimensions and identifying the weaknesses that need repair before users arrive.
Secrets deserve particular scrutiny because a hardcoded API key in a public repository can be exploited within minutes by automated scanning. Service accounts, API keys, and integration tokens need governance separate from human passwords. Store them in a secrets manager, rotate them automatically, and audit them regularly. Development, staging, and production should have distinct credentials so a development compromise does not expose production donor data.
For an organization without internal engineering capacity, the partner’s scope should include auditing and rebuilding unsafe authentication, then maintaining it. Launch is only the first threshold of reliability. The credential architecture in place at launch tends to stay unless someone chooses to change it, so an assessment before signing an engagement helps spell out the work needed beyond making the application run.
Writing a credential policy that staff will actually follow
Implementation should make the safe action the easy one. Provide the password manager, make MFA enrollment the default rather than opt-in, and guide staff toward tools with stronger access controls. Those choices turn a requirement into a supported way of working. Otherwise, the policy asks people to overcome the same constraints that caused the problem.
Keep the written policy short and plain. A one-page document with the basic rules and the name of the person in charge gives staff more help than a file that covers everything but goes unread. Explain what the rules protect, including donor trust, client privacy, and the funds that keep programs running. Give the named owner authority to enforce the rules, including revoking access when offboarding procedures are not followed.
The document also needs a review date, at least annually, and a quarterly check of MFA enrollment across Tier 1 and Tier 2 accounts. Tools and staff will change even when the wording does not. The first step is manageable. Name the owner and inventory the highest-risk accounts, then use that inventory to identify where access cannot yet be controlled.
Notes
- Cybersecurity Best Practices for Nonprofits
Covered the cybersecurity risks nonprofits face, including donor and client data exposure, credential weaknesses, phishing, and limited IT capacity.


