Could the Wrong Person Access Your Data?

A volunteer needs access to your mailing list. That makes sense. But can they also see donor amounts, pastoral notes, health information, or details about the families you support? Most data-security problems do not begin with someone deliberately doing the wrong thing. They begin when access is broader than it needs to be, an old account is never removed, or a rushed team member clicks a convincing link.

For churches, charities, and community organisations, the information you hold is often deeply personal. Protecting it starts with one practical question: can each person see only what they genuinely need to do their role?

Start With What People Need

Giving everyone the same level of access may feel simpler, especially in a small team, but it creates unnecessary risk. Your worship team may need contact details and roster information without needing access to giving records. A programme volunteer may need attendance information without seeing private case notes. A fundraiser may need donation history without access to sensitive client details.

Work from the role rather than the person. List what someone needs to view, add, edit, export, or delete, then give them the lowest level of access that still allows them to do their job properly.

Review Access When Roles Change

Access that was appropriate six months ago may not be appropriate now. Staff leave, volunteers change teams, contractors finish projects, and people take on new responsibilities.

Build access checks into your normal handover process. Remove accounts promptly when someone leaves, update permissions when a role changes, and review high-access users regularly. Do not rely on someone remembering to tidy it up later.

Strengthen Every Sign-In

Use a long, unique password or passphrase for every account, ideally stored in a reputable password manager. Current guidance does not recommend changing strong passwords on a routine schedule simply for the sake of it. Change them when there is evidence or suspicion of compromise, and never reuse them across services.

Multi-factor authentication adds another barrier if a password is stolen. It is especially important for administrators and anyone who can access, export, or change sensitive information.

Protect the Whole Access Path

Cloud software can keep the platform itself updated, but security still depends on the devices, email accounts, and internet connections your team uses to reach it. Keep computers and phones updated, use supported software, lock devices when unattended, and protect the email accounts used for password resets.

A VPN can be useful in some situations, but it is not automatically essential for every organisation or every connection. The more useful starting point is understanding how people access your systems and addressing the actual risks.

Know What Is Backed Up

A cloud system being backed up does not necessarily mean every mistake can be instantly reversed or that you have your own independent copy of everything. Ask what the provider backs up, how recovery works, how long deleted data is retained, and what your organisation should export for its own records.

Make sure those exports are protected too. A spreadsheet full of donor or client information saved to someone’s personal laptop is still sensitive data.

Make Phishing Easier to Spot

Phishing messages are designed to create urgency: a payment has failed, a password is about to expire, or a senior person needs something immediately. Encourage people to pause, check the sender carefully, and confirm unusual requests through another channel before clicking or sharing information.

Keep training short and practical. A five-minute reminder using a realistic example is often more useful than an annual policy nobody remembers.

Check the Audit Trail

Security is not a set-and-forget task. Review who has access, look for unusual activity, and make sure changes to important records can be traced. Audit trails are useful not because you expect the worst from your team, but because they help you spot mistakes and understand what happened.

Collect Less, Protect Better

The safest sensitive information is often the information you never needed to collect. Be clear about why each field exists, who will use it, how long it should be kept, and whether people have consented to that use. Privacy obligations differ across countries, so make sure your practices fit the laws that apply to your organisation.

The Bottom Line

Good data security is not about making everyday work impossible. It is about creating sensible boundaries so staff and volunteers can do what they need without seeing what they do not.

infoodle gives organisations control through role and field permissions, multi-factor authentication, and audit trails, helping you keep access practical without treating every user the same. When the right people can reach the right information – and no more – you protect both your data and the trust behind it.