Protect your mission and the information people trust you with.

Start with how your organization works.

Staff and volunteer onboarding, donor-data access, shared mailboxes and budget-conscious licensing decisions.

We agree the systems and responsibilities in scope, identify the gaps and build a practical plan around the people who will carry it out. That can include Microsoft 365 administration, vendor oversight, protection of donor and constituent data, and recovery planning. We scope work around your mission, staffing and budget. Any nonprofit terms and Microsoft licensing eligibility are confirmed separately.

When you need one accountable team across technology and security, ask about our Outsourced Security & Technology Management engagement. A focused project or support alongside an existing IT provider is also available.

WHAT ONGOING MANAGEMENT LOOKS LIKE

Setting Microsoft 365 up correctly is the start. Keeping it right is the work.

Under an agreed scope, we take responsibility for:

• Confirming that sign-in, admin and sharing settings are still configured the way you approved.
• Reviewing security alerts and agreeing with you what needs action.
• Routine maintenance, license changes and accounts as people join and leave.
• Reporting what we checked and what changed, in plain language a director or board can read.
• Coordinating your other vendors so one team is accountable across all of it.

Your organization keeps ownership of its accounts, data and licenses. We manage them for you and answer for that work.

This fits nonprofits with roughly 5 to 40 staff and volunteers who need technology leadership but not a full-time IT department.

WHAT WE SEE IN NONPROFITS

Small staff, many hands, and nobody responsible for IT

Nonprofits often run with a few paid staff, a rotating group of volunteers, board members who need occasional access and a mix of donated or discounted tools. That works until someone leaves, a funder asks a security question or an insurance renewal arrives.

• Volunteers are given accounts quickly, but nobody removes them when they stop helping.
• Donor and client information sits in shared mailboxes, spreadsheets and personal OneDrive folders.
• One staff member, or a board member, holds every admin password.
• A grant, funder or insurer asks about security controls and the answers are a guess.
• There is no one to call when something goes wrong.

We wrote about that last point in most nonprofits have no one to call when something goes wrong.

A PRACTICAL STARTING POINT

A handoff a nonprofit director can actually review

One of the most useful things a small nonprofit can do is make account changes someone’s job. This illustrative example shows what a staff or volunteer departure can look like when responsibilities are clear.

Step	Who is responsible (example)
Approve the departure and the end date	Executive director or program lead
Remove sign-in access and active sessions	Microsoft 365 administrator
Hand over mailbox, files and shared resources	Administrator, with the person taking over the work
Preserve records the organization needs to keep	Data owner, following your retention requirements
Confirm it is finished and recorded	A second person, such as operations or finance

Your roles will be different. The point is that every step has a name next to it.

If you are working through a renewal, our guide to cyber insurance readiness for PG County nonprofits and the cyber insurance readiness checklist are good places to start. The nonprofit cybersecurity starter guide covers the basics.

NexSecure is based in Bowie, Maryland and supports nonprofits in Prince George’s County, across Maryland and across the US, mostly remotely. Microsoft nonprofit pricing and eligibility are set by Microsoft and confirmed separately through its nonprofit program.