Cloud storage for nonprofits: grants, ownership, and recovery

Cloud storage for nonprofits should keep shared files accessible when staff change, volunteers leave, or someone deletes the wrong folder. A free storage allowance helps, but the more useful questions are who controls the account, who can open each file, and how the organization will recover its records.

Start with the tools your team already uses. Compare Google Workspace for Nonprofits, Microsoft 365 nonprofit offers, and Box.org against the same requirements: eligibility, shared storage, permissions, recovery, and the cost of running the service. This guide focuses on everyday file storage for small nonprofit organizations, rather than CRM software or cloud computing credits.

Compare nonprofit cloud storage offers

The offers below were checked against provider documentation on October 28, 2026. Availability, eligibility, and terms can change. Confirm the offer in your country before moving files or canceling an existing subscription.

Google Workspace for Nonprofits

Google's no-cost nonprofit edition includes 100 TB shared across the organization. It combines Google Drive with email and document collaboration. Shared drives are included, making it worth evaluating for teams already using Google Docs.

Check the exact edition when comparing administrative controls. The free edition does not include every retention, audit, or access-control feature offered in paid plans. Large capacity alone does not establish that a plan meets your organization's requirements.

Microsoft 365 nonprofit offers

Microsoft documents up to 300 donated Business Basic licenses. The Business Basic plan includes 1 TB of OneDrive storage per user and web and mobile productivity apps. This can suit an organization already working with Microsoft documents.

Do not treat those personal work-account allowances as one shared storage pool. Check SharePoint capacity separately for team libraries, and confirm whether staff need desktop Office applications or security features that require a different plan.

Box.org

Box.org's donated Starter offer supports up to 10 users and lists 100 GB of storage, a 2 GB upload limit per file, and 25 file versions. Eligibility requires recognized nonprofit status and TechSoup validation. Discounted paid plans are also available.

Evaluate this option for a small team with modest file-storage needs. A library of large video recordings could exceed Starter's limits quickly. Check external collaboration terms and the controls included in the specific plan before choosing it for sensitive work.

Check who qualifies before counting free seats

Nonprofit pricing depends on both the organization and the people using the licenses. Registration as a charity does not guarantee access to every donated product. Review country coverage, excluded organization types, validation documents, and renewal conditions directly with each provider.

Microsoft's nonprofit licensing FAQ distinguishes donated licenses for paid employees and eligible unpaid executive leadership from discounted licenses available to volunteers. Guest access may cover some collaboration needs. Do not assign a donated staff license to every volunteer by default.

For example, a charity with five employees and 20 occasional volunteers should map the tasks each group performs before choosing licenses. Some volunteers may only need access to an event folder. Others may need an organization email address and editing tools. Price those needs separately and test guest access with a representative volunteer.

Keep the eligibility decision, renewal date, and billing contact in an organization-controlled location. Assign someone to review provider notices. A grant or discount can change, and a license transition may require action even when the organization remains eligible.

Measure shared storage separately from individual storage

Make a simple inventory before comparing capacity. Record current file size, expected annual growth, largest individual file, and the people who need access. Separate working documents from media archives, financial records, grant proposals, and beneficiary records.

Pooled storage gives an organization a shared allowance. Per-user storage gives each licensed account its own allowance. Neither figure tells you, by itself, how much space a particular team library can use or how long deleted material remains recoverable.

A practical comparison sheet should include:

• Storage available to shared team locations, with any separate quotas.
• Maximum file size and the behavior of large uploads on your connection.
• Version-history limits and whether versions consume storage.
• Offline access requirements for staff working with unreliable internet.
• The cost of additional capacity and accounts as the team grows.

Include an example from your own work in the trial: a spreadsheet edited by several people, a scanned grant agreement, or a folder of event photographs. A service that handles ordinary office documents well may need a different plan for large media files.

Keep shared records under the organization's control

The person who creates a file should not become the only person who can preserve it. Avoid keeping the sole copy of board records, donor data, or project documentation in a volunteer's personal account.

Google documents that shared-drive files remain when a member leaves. For Microsoft teams, evaluate a SharePoint library for shared records, and use the documented OneDrive-to-SharePoint transfer options when moving working files into team ownership. Test permissions and links after any move.

For whichever service you choose, document who administers each shared space and how a replacement administrator gains access. Have at least two authorized people able to handle an administrator's absence, using separate named accounts. Protect the domain registration, billing account, and recovery methods as well as the files themselves.

Use a volunteer handover checklist

1. Identify the files, shared folders, and external accounts used for the role.
2. Move or transfer organizational records into the agreed shared location while access is still available.
3. Have the incoming person open representative files and check that needed links still work.
4. Remove the departing person's access, active sessions, and group memberships through the service's controls.
5. Check public links, external shares, and connected applications separately.
6. Retain or delete the former account according to the organization's documented retention process.

Assign a named owner and completion date to this process. Simply changing a shared password leaves uncertainty about downloaded copies, connected apps, and who still has access.

Set permissions around the work and the data

A fundraising volunteer may need approved campaign images without needing the donor spreadsheet. An external accountant may need finance records without access to beneficiary case files. Build folders and access groups around these actual boundaries.

Use named invitations for restricted material, limit editing rights to people who need them, and review external partners' access when a project ends. Require multifactor authentication where supported and document a recovery process that does not depend on one person's phone.

If you handle highly sensitive data, involve the person responsible for privacy and information security before migration. Ask about data locations, access logging, retention controls, contractual terms, and the consequences of downloading files to personal devices. A provider's certification or encryption claim does not settle whether your particular configuration is appropriate.

Give staff a short sharing guide with examples: where to put a draft grant proposal, which folder holds approved public materials, and who can authorize access to restricted records. Practical instructions are easier to follow than a long policy that does not match daily work.

Test recovery before relying on cloud storage

Synchronization can carry an unwanted change or deletion across devices. Version history and trash recovery can help, but they have limits. Google, for example, documents a 25-day administrator recovery window after a user empties Drive trash. Account deletion and other recovery situations have different rules.

List the records you cannot afford to lose and decide how much recent work you could recreate. Then check whether the chosen plan can meet that need. Consider a separate backup with suitable retention and independent access for critical records. Our cloud backup guide explains the recovery questions to ask.

Run a small test using non-sensitive sample files. Delete one file, overwrite another, and restore both through the documented process. Check the recovered contents and permissions, record how long it takes, and identify who can repeat the procedure if the main administrator is unavailable.

Repeat the test after major configuration changes. A backup dashboard reporting success is useful evidence, but opening a restored file gives you a more direct check that the recovery process works.

Budget for administration and an eventual move

Compare annual operating cost, including paid seats, extra storage, backup, migration support, and staff time. Free licenses still leave work to do: onboarding volunteers, reviewing shares, answering access questions, and handling departures.

Keep an exit plan alongside the budget. Record how to export files, which formats you will use, and what may not transfer, such as sharing links, comments, permissions, or version history. Test a small export before committing the full library. Our cloud-to-cloud migration guide covers checks for the destination copy.

For a pilot, choose one team and a bounded folder rather than the entire organization. Agree on success criteria: the right people can open and edit files, restricted files remain restricted, a restore succeeds, and someone other than the setup administrator can manage access. Keep the source copy until those checks pass.

Questions to settle before choosing a service

What is the best cloud storage for nonprofits?

Start by testing the eligible offer that fits your existing productivity tools. Choose it only if the shared-file ownership, permissions, capacity, recovery, and ongoing administration meet your needs. Moving to a different service is worthwhile when it solves a documented problem that the current setup cannot address at a reasonable cost.

Can volunteers use the same storage as employees?

Often they can collaborate on selected files, but account eligibility and access rights are separate decisions. Check the provider's rules for donated licenses, paid licenses, and external guests, then give each person only the access needed for their role.

Does free cloud storage replace a backup?

A free allowance does not tell you what can be restored after deletion, account loss, or a missed license renewal. Check the recovery terms, test the process, and keep a separate recoverable copy where the consequences of losing records justify it.