Why the Pretoria team asked for help
The client was a small professional services team in Pretoria handling daily client work across several cloud applications, message, file storage and internal admin tools. Their passwords were being tracked in spreadsheet files and a few shared notes, which made access hard to control when people joined, changed roles or left.
They wanted a practical setup, not a complicated security project that would slow everyone down. The brief was clear: reduce password sharing, give administrators proper control, and make it easier for staff to sign in to the systems they use every day without calling for help each time. They also wanted remote support because part of the team worked from home and the office had mixed internet stability during load-shedding.
- Client type: small business professional services team
- Town: Pretoria, with some staff working remotely
- Core issue: spreadsheet-based password storage and weak access control
- Priority: simple sign in, better oversight and less admin time
What had to work in a small business environment
The biggest constraint was time. The team could not stop normal work for a long migration, and they did not have a dedicated internal IT person to manage every step. Some users were comfortable with technology, others were not, so the rollout had to be straightforward and easy to repeat for new starters. We also had to make sure access changes would be easy to handle later, especially when contractors or temporary staff were involved.
Security mattered, but so did practicality. The setup had to support proper admin separation, fewer shared credentials and a cleaner offboarding process. The client also asked for a structure that would work across office and remote users without creating a mess of different rules for each person.
- No long downtime window available
- Mixed user comfort with new software
- Remote and office-based staff
- Need for simple offboarding and handover controls
How we structured the rollout
We started with an initial security review to map what systems were in use, who needed access, and where the current process was weakest. From there we designed the vault structure, mapped permissions and set up the administrative roles so that access could be managed properly from day one. We then moved the team away from spreadsheet password lists and into a controlled password manager with single sign-on for the main business applications.
The migration was handled in stages to keep disruption low. First, we moved the most critical credentials, then we checked each shared app and updated the sign-in flow. After that, we trained administrators on daily use, recovery steps and how to add or remove users cleanly. The service team in Pretoria could then run the account structure without needing constant support.
- Initial Security Review
- Platform Setup and SSO Configuration
- Vault Structure Design and Permission Mapping
- Password Migration for priority accounts first
- Admin Training and User Onboarding Training
Timeline and key milestones over four weeks
The project ran over four weeks from first review to handover. Week 1 focused on discovery, account mapping and the security review. Week 2 covered platform setup, permission design and the first round of user onboarding. Week 3 was used for password migration, sign in testing and adjustments where teams had different access needs. Week 4 focused on admin handover, offboarding process design and final support for users who needed extra help.
Because the team was spread between office and remote work, we kept sessions short and practical. The support team used remote onboarding sessions and follow-up checks so that staff could get through the change without interrupting client work. That approach worked well even when load-shedding caused a few delays in the day.
- Week 1: review and access audit
- Week 2: setup and permissions
- Week 3: migration and testing
- Week 4: training and handover
What changed after the new setup went live
After the rollout, the team no longer depended on open spreadsheet lists for passwords. Administrator controls were tighter, access was easier to trace and shared credentials were reduced to the minimum needed for business use. Staff also had a cleaner sign in experience because the main applications were tied into single sign-on rather than multiple separate passwords.
The practical effect was less time spent asking for access, fewer mistakes when someone moved roles and a better offboarding process when a user left. The client reported that internal admin tasks became quicker and that managers had more confidence in who could see what. It also became simpler to support new staff because the process was now repeatable and not based on memory or a file saved on one person's laptop.
- Removed risky spreadsheet password lists
- Improved control over administrator access
- Reduced access-related interruptions
- Made onboarding and offboarding easier to manage
What we would do again for another Pretoria team
We would use the same method again for any small Pretoria business that needs better access control without overcomplicating things. Start with a proper review, keep the permission model simple, migrate the most important accounts first and train the people who will actually run the system. That sequence keeps the project practical and helps the team settle in quickly.
For companies in Pretoria and other South African towns, this approach works best when the team has a mix of office and remote staff, limited internal IT support and a real need to stop using shared files for sensitive information. A good rollout should be tidy, predictable and easy to maintain after handover.
- Best for teams of 5 to 50 users
- Works for office and remote staff
- Useful where admin control needs to improve fast
- Suitable for small businesses without full-time IT staff
Key facts
| Client type | Small business professional services team |
|---|---|
| Town | Pretoria |
| Timeline | 4 weeks |
| Scope | Password management and single sign-on rollout |
| Key issue | Spreadsheet-based password lists |
| Delivery | Remote onboarding with admin training |
