- Charities mix paid staff, volunteers and trustees, so a provider must be good at setting people up, giving them only the access they need and closing accounts when they leave.
- Charity Commission guidance notes that many charities 'store sensitive data about employees, volunteers, donors and beneficiaries'.
- HMRC: 'You must keep a record of declarations for 6 years after the most recent donation you claimed Gift Aid on', so donor records and their backups matter for years.
- The Commission says trustees may delegate cyber security, for example to an IT team, 'But all the trustees remain responsible for making sure your charity is protected.'
- The Commission's trustee guidance (CC3) says trustees must use reasonable care and skill, 'taking appropriate advice when necessary', and should ensure accountability where tasks are delegated to staff or volunteers.
- Charities must report serious incidents to the Commission; its examples include cyber-crime and significant data breaches or losses.
- If an IT provider processes personal data for the charity, UK GDPR Article 28 requires a processor contract.
What makes IT support for a charity different?
The people, the data and the money. Charities rely on volunteers and part-time staff, hold records about donors and the people they help, answer to a trustee board, and often pay for IT out of restricted or short-term funding. Good support is built around all four.
| Area | In many businesses | In many charities |
|---|---|---|
| People | Mostly salaried staff on fixed contracts | Paid staff, volunteers, sessional workers and trustees, some working a few hours a month |
| Turnover of users | Occasional joiners and leavers | Volunteers join for a project or a season, then leave, often without notice |
| Data | Customer and supplier records | Donor, member, volunteer and beneficiary records, Gift Aid declarations, sometimes safeguarding notes |
| Decision-making | Owner or directors decide | Trustees decide, often meeting quarterly; a manager runs things day to day |
| Funding for IT | From trading income | Unrestricted reserves, or a grant with its own rules on what it can pay for |
| Places | One office or hybrid | An office plus shops, community venues, events and people's homes |
None of this needs exotic technology. It needs a provider that is disciplined about accounts, documents everything so knowledge doesn't leave with one volunteer, and explains costs in a way a trustee board can approve.
How should a charity handle accounts for volunteers, joiners and leavers?
Give everyone who touches charity data their own named account with only the access their role needs, avoid shared logins wherever you can, and run the same short checklist every time someone starts or leaves. A good IT provider makes this routine rather than a scramble.
Shared logins (one 'volunteers' email account, or a single password for the donor database written on a card) are the most common account problem in charities. They feel convenient, but you can't tell who did what, you can't remove one person without changing it for everyone, and the password tends to live on long after people have gone.
Shared logins
- No record of who opened or changed a record
- Removing one leaver means resetting it for everyone
- Passwords get written down and passed on
- Hard to add multi-factor sign-in
Named accounts
- Each action is traceable to a person
- A leaver is switched off in minutes
- Sign-in protection works per person
- Access can match the role, and expire
- Starter The volunteer coordinator or manager asks for an account using a simple form: name, role, start date, what they need to reach (email, a shared folder, the donor system), and an end date if the role is fixed-term.
- Least access The provider sets the account up with only that access, plus multi-factor sign-in. Fundraising volunteers don't need the HR folder; a shop volunteer may need nothing but the till and a rota.
- Devices Agree whether volunteers use charity laptops or their own phones and computers, and what they may store on a personal device.
- Review Every few months the provider sends a list of active accounts so someone can confirm who still volunteers.
- Leaver On the last day, or as soon as you know someone has drifted away, the account is blocked, files and mailbox are handed to a named person, and any charity devices come back.
What should IT support do to protect donor, beneficiary and Gift Aid records?
Know where every copy of that data lives, keep it in a system with proper accounts rather than scattered spreadsheets, back it up in a way you can actually restore, and make sure the charity can always get its data out. HMRC requires Gift Aid declarations to be kept for six years after the last donation claimed on.
The Charity Commission's cyber crime guidance points out that many charities 'store sensitive data about employees, volunteers, donors and beneficiaries', and that this makes them an attractive target. In practice, the bigger day-to-day risk is often untidiness: donor lists exported to a volunteer's laptop, three versions of the mailing list, and nobody sure which is current.
If your IT provider can access, store or back up personal data for the charity, it processes that data for you, and UK GDPR Article 28 requires a contract that, among other things, has it act only on your documented instructions. Article 32 also expects 'the ability to restore the availability and access to personal data in a timely manner' after an incident.
What are trustees responsible for when it comes to IT?
Charity Commission guidance says trustees must manage the charity's resources responsibly, use reasonable care and skill and take advice when needed. They can delegate IT and cyber security, to staff or a provider, but they remain responsible, and they must report serious incidents, which can include significant data losses.
- Prudence. The Commission's guidance The essential trustee (CC3) says trustees 'must act responsibly, reasonably and honestly', including to 'avoid exposing the charity's assets, beneficiaries or reputation to undue risk'.
- Care, skill and advice. CC3: trustees 'must use reasonable care and skill, making use of your skills and experience and taking appropriate advice when necessary'.
- Delegation. The Commission's cyber crime guidance: 'You may be able to delegate cyber security to someone else at your charity, such as an IT team. But all the trustees remain responsible for making sure your charity is protected.'
- Set expectations. The same guidance says trustees should decide what their expectations are and make sure they are met, adding that these 'will depend on the size of your charity and the resources it has'.
- Accountability. CC3 says trustees should ensure accountability 'particularly where you delegate responsibility for particular tasks or decisions to staff or volunteers'.
- Serious incidents. 'The Charity Commission requires charities to report serious incidents.' Its examples include cyber-crime and 'significant data breaches/losses', where significant means significant 'in the context of your charity'.
For IT support, that translates into something simple: trustees should receive a short, plain-English report they can understand and question. Ask any provider to show you an example of the report they would give your board: what was fixed, what's out of date, whether backups were tested, and what decisions they need from you.
How can a small charity get good IT support on a tight budget?
Decide what really must work every day, pay for proper support for that, and keep the rest simple. Ad hoc help or block hours can suit a very small charity; a monthly managed service suits one with staff relying on systems daily. Whatever you choose, make sure the charity, not a volunteer or supplier, owns its accounts.
Many small charities run on a generous volunteer who 'does the IT'. That can work well, until they move on and nobody knows the admin password, which personal email the domain is registered to, or where the backups are. Before you spend anything, write down who holds the keys.
- Own your accounts. The charity's domain name, Microsoft 365 or other email tenancy, admin accounts and software subscriptions should be in the charity's name, with at least two trustees or senior staff able to reach the admin details.
- Prioritise. Email, the supporter database, online giving and the shared files usually matter most. Pay for reliable support on those first.
- Match the model to the funding. If IT is paid for from a time-limited grant, ask for terms that let you scale down or leave when the grant ends, rather than a long fixed contract.
- Ask about charity pricing, then check it. Some providers and software vendors offer charity terms. Ask what they are in writing, what eligibility they depend on, and what happens to the price later.
- Use free official guidance. The Commission points small charities to the NCSC's free Cyber Action Toolkit, which covers basics such as protecting devices and backing up data.
Questions to ask an IT provider before working with your charity
Have you supported charities with volunteers? How will you handle starters and leavers? Do you know our supporter database? What will you report to trustees? Will you sign a processor contract? How do we leave, and how do we get our data back?
Volunteers
How they set up, review and remove accounts for people who only help occasionally.
Charity software
Whether they've worked with your fundraising, membership or case management system, and its supplier.
Trustee reporting
A sample board report, and whether they'll attend a trustee meeting if asked.
Contract length
Notice periods and whether terms fit grant funding that may end.
Data protection
A UK GDPR processor contract and a clear list of who can access your data.
Restores
When they last tested restoring a supporter database, and how long it took.
Get quotes for business IT support
Tell us about your business and the IT support you need, once. We pass it to a UK IT support provider (a managed service provider), who will:
- Talk through your setup: staff, devices, sites, Microsoft 365 or other systems, and what keeps going wrong.
- Quote in writing, showing how it's priced (per user, per device or hours), what's included and what's extra.
- Set out the service levels: help desk hours, response and fix targets, onboarding and how you leave.
For businesses and organisations. Prefer email? Write to [email protected] with your staff numbers, sites and the support you need.
Related guides
IT support for charities: frequently asked questions
What IT support does a small charity need?
Reliable email and shared files, support for your supporter or membership database, a simple process for volunteer accounts, backups that can be restored, and someone to call when things break. Many small charities start with ad hoc help or block hours and move to monthly support as they grow.
Should volunteers have their own email accounts?
Anyone who handles charity data should ideally have their own named account, so you know who did what and can switch off one person without affecting everyone else. Some volunteers may need very little access, so ask the provider which roles need a full account.
Is it OK for volunteers to share one login?
It's common but risky: you can't see who made a change, removing a leaver means changing the password for everyone, and shared passwords spread. Named accounts with only the access each role needs are easier to manage and protect.
How long must a charity keep Gift Aid declarations?
HMRC says you must keep a record of declarations for six years after the most recent donation you claimed Gift Aid on. Your IT setup and backups need to keep those records safe and findable for that long.
Are trustees responsible for a charity's IT?
Charity Commission guidance says trustees can delegate cyber security, for example to an IT team, but all the trustees remain responsible for making sure the charity is protected. They must use reasonable care and skill and take advice when necessary.
Do we have to report a cyber attack to the Charity Commission?
You may need to. The Commission requires charities to report serious incidents, and its examples include cyber-crime and significant data breaches or losses. Its guidance also says to report cyber crime to Report Fraud. Read the Commission's serious incident guidance to decide.
Can an IT provider support our fundraising database?
Usually, alongside the software supplier. The provider looks after accounts, devices, access and backups; the supplier supports the application itself. Ask any provider which charity systems they have worked with.
Do we need a data processing contract with our IT provider?
If the provider can access, store or back up personal data for your charity, it is processing it for you, and UK GDPR Article 28 requires a contract setting out what it may do with that data.
Do IT support providers offer charity discounts?
Some do, and some software vendors have charity terms. We don't publish prices or make claims about any scheme, so ask each provider to put any charity pricing and its conditions in writing.
Do you recommend IT providers for charities?
We introduce your charity to a UK IT support provider for a quote. We don't endorse or rank providers, and there's no obligation.
Sources
We checked the facts on this page against these sources on 18 November 2026. Guidance changes: check the current version before you rely on it.
- Protect your charity from cyber crime (GOV.UK, Charity Commission)
- The essential trustee: what you need to know, what you need to do (CC3) (GOV.UK, Charity Commission)
- How to report a serious incident in your charity (GOV.UK, Charity Commission)
- Claiming Gift Aid as a charity or CASC: Gift Aid declarations (GOV.UK, HMRC)
- UK GDPR Article 28: Processor (legislation.gov.uk)
- UK GDPR Article 32: Security of processing (legislation.gov.uk)