A small Gqeberha team needed less admin and tighter control
The office was based in Gqeberha and ran with a lean team that handled outreach, donor admin and programme coordination from the same limited set of devices. Their main issue was familiar: passwords were being kept in notes, shared over chat and reset too often, which created risk and wasted time. They wanted a cleaner way to store access, share logins where needed, and remove people properly when roles changed.
We started with an Initial Security Review and a short working session with the office lead, the admin staff and the person handling systems. The brief was practical. Keep it simple, keep it affordable, and make sure the team could use it without calling for help every day. There was no appetite for a long rollout. They needed something that could be introduced in stages and still work well for a small office with irregular schedules and limited in-house IT support.
- Client type: nonprofit office
- Location: Gqeberha
- Team size: 8 users
- Rollout model: remote first with live guidance
- Main need: central password control and basic single sign-on
What we set up for the office
We supplied a structured vault setup, single sign-on configuration for core applications and a permission map that matched actual job roles. Instead of giving everyone broad access, we split items by function so finance, programmes and management each had the right level of visibility. That helped reduce confusion when someone was away on leave or working from home in town.
We also designed an offboarding process so access could be removed quickly when a temporary contract ended. This matters for small organisations where people often move between projects or leave on short notice. The office now has a clear path for new starters, role changes and exits, with less chance of old logins hanging around for months. It sounds basic, but it saves a lot of trouble later on.
- Vault structure built around departments and shared services
- Permission mapping for admins, team members and managers
- SSO setup for the main daily-use applications
- Password migration from ad hoc storage into one secure system
- Offboarding steps for departing staff and volunteers
Training that fit a busy nonprofit rhythm
Training was done in short remote sessions so people did not have to stop work for half a day. We covered daily use, how to find shared access, how to handle a reset, and what to do when a new staff member joins. The goal was confidence, not jargon. The team did not need a security lecture, they needed straight answers and a routine they could follow on a Monday morning.
We also trained one admin lead and one backup user on the rules for approving access, changing permissions and checking the vault structure. That way the office would not depend on a single person for everything. The support lead in our side stayed available during the first few weeks for quick fixes and follow-up guidance, which was useful when people were moving between devices or dealing with load shedding interruptions.
- User onboarding training for the full team
- Admin training for access changes and approvals
- Simple step-by-step handover notes
- Remote support during the first month
Timeline, delivery and the main constraints
The full rollout took 3 weeks from first review to final handover. Week 1 covered the review, system planning and agreement on roles. Week 2 handled setup, migration and permissions. Week 3 focused on training, live testing and a final check with the office lead. The pace suited the team because it did not interrupt donor reporting or fieldwork.
The main constraints were straightforward. They had a small team, shared responsibilities and no spare capacity for a complicated changeover. There was also a need to keep sensitive data contained, because nonprofit offices often handle personal information, donor records and internal notes in the same working environment. We worked around that by keeping the structure tight and the access rules clear. It was not flashy, just practical and steady.
- Week 1: review and planning
- Week 2: setup, migration and permissions
- Week 3: training and handover
- Support model: remote with local response during rollout
Results the office could feel straight away
The biggest win was less time spent chasing passwords. Staff could get into their tools faster, shared access was no longer passed around in chat messages, and the admin lead had a proper way to see who had access to what. The team also felt more confident about staff changes because the offboarding steps were already laid out.
For a small nonprofit, that kind of order matters. It reduces the risk of someone using an old password after leaving, and it removes the stress of wondering where a login is stored. The office also told us the structure made it easier to train temporary help when they had a busy month. That is often where the mess starts, so having one clear system made a real difference.
- Faster access for daily applications
- Less reliance on shared notes and informal chats
- Clearer control for admin and management
- Better handover for temporary staff and volunteers
What we would repeat for another nonprofit office
If we were starting this kind of project again, we would use the same approach. Keep the permission structure simple, build around actual job duties and make sure the admin lead can carry the process without outside help every day. That is the right fit for small organisations that need security but not complexity.
We would also repeat the short training format and the staged rollout. It gives people time to adjust, and it avoids the common problem of introducing too much change in one go. For nonprofit teams in Gqeberha and other cities, that balance is important. They need a system that works during busy weeks, during power cuts, and when someone is working remotely from home or from a partner site.
- Keep the setup lean and role-based
- Train one admin and one backup person
- Introduce offboarding from day one
- Use short support windows after handover
Key facts
| Project type | Nonprofit office access management |
|---|---|
| Town | Gqeberha |
| Timeline | 3 weeks |
| Users onboarded | 8 |
| Core services | Initial Security Review, Platform Setup, SSO Configuration, Vault Structure Design, Permission Mapping, User Onboarding Training, Admin Training, Password Migration, Offboarding Process Design |
| Support model | Remote onboarding with practical local support |
