Why the Salt River office asked for a clean-up
The brief came from an accounting practice in Salt River, Cape Town that was juggling too many shared logins, old spreadsheets with passwords and different access habits across departments. The partners wanted a proper structure before year end pressure kicked in, and they needed something staff could actually use every day without slowing the office down.
Like many small firms, they had grown by adding apps one at a time. Payroll, bookkeeping, document storage and tax tools had all been introduced at different times, so access had become inconsistent. One person might leave the office and still know a live password, while another had to ask around just to get into a system. That was not good enough for client data, and it was causing admin delays too.
The main goals were simple: reduce password sharing, give each person the right level of access and make logins easier for the team. They also wanted a setup that would work during load-shedding and with remote staff checking in from home or on the road.
What we had to work around
The office had a few constraints that shaped the rollout. First, staff could not all stop work at once, so the change had to happen in stages. Second, some users were not very confident with new admin tools, so the training had to be plain and practical. Third, the firm needed a clear offboarding process for temporary staff and article clerks who come and go through the year.
We also had to keep the structure tidy enough for monthly reviews. In an accounting office, permissions can get messy quickly if each department handles access in its own way. We worked with the partners and team leads to map access by role, not by habit, which made the whole system easier to manage.
- 40 users across finance, payroll, admin and client service functions
- Hybrid working pattern with some remote access required
- Shared client information needed tighter protection
- Login and access habits had to be simple enough for daily use
- Office operations could not stop for a long handover
How the rollout was handled week by week
The project ran over 3 weeks. In week one we carried out the initial security review, checked current password habits and listed the main applications in use. We then built a vault structure around departments and working groups, so the office had one clear place for critical credentials instead of several scattered systems.
In week two we handled platform setup, permission mapping and single sign-on configuration. Users were grouped by function, with partners, accountants, payroll staff and support staff each getting different access. We also moved the most important admin credentials into controlled vault areas so they could be tracked and updated properly. A few legacy logins had to be cleaned up, which took some back and forth with the client but it was worth it.
Week three focused on password migration, user onboarding training and admin training. The team learned how to save credentials, approve access requests and use the sign-on flow correctly. We also set up the offboarding process design so that exits, role changes and temporary access could be handled without relying on memory.
- Initial Security Review
- Platform Setup and SSO Configuration
- Vault Structure Design
- Permission Mapping by role
- Password Migration and training sessions
What changed for the team after go-live
Once the new structure was live, the office moved away from shared passwords and ad hoc access requests. Staff could sign in with a clearer process, and managers had a better view of who could reach which tools. That made day to day work quicker, especially when people were helping each other during busy periods or when someone was away from the office.
The biggest change was probably peace of mind. Client records, tax work and internal admin now sat behind a more controlled system, so it was easier to see what was in use and who had access. The partners also had a cleaner process for quarterly access reviews, which meant permissions would not drift over time. That matters in accounting, where staff changes and client deadlines can make things messy fast.
There was also a practical benefit for load-shedding days and remote work. Because the team had a clear login process and fewer password bottlenecks, people could get back to work quicker after interruptions. Not every business needs a complicated security setup, but every business does need one that staff will actually use.
Support, training and the human side of access
We kept the training focused on everyday tasks rather than theory. The aim was to make the system easy enough for a busy accounting office to use without calling for help every time a password needed updating. Zinhle handled the training coordination, while Zaheer led technical support for any user issues that came up during the first few days.
Siyanda and Revasha worked with the client on the service side, making sure questions were answered quickly and that the office had a clear contact path for support. Kgosi handled implementation details and Ruan checked the security structure, including how access was separated for different functions. That mix of admin, support and technical work kept the rollout steady.
What helped most was keeping the process practical. We did not overcomplicate the setup or bury the team in policy language. Instead, we showed them how to manage access in a way that fits a real office with deadlines, client work and changing staff needs.
- User Onboarding Training for day to day use
- Admin Training for partners and office leads
- Quarterly Access Reviews for ongoing control
- Ongoing Team Support from the Cape Town base
What we would do again for a similar firm
If we were setting up another accounting office in Salt River, Stellenbosch or Johannesburg, we would follow the same approach again: review the current access, sort users by role, move the essential logins into a controlled vault and train the team before go-live. That order works because it keeps disruption low and gives the office a proper handover.
For a firm like this, the best results come from clear rules and simple habits. We would again recommend a structured offboarding process, monthly or quarterly access checks, and a single sign-on plan that reduces password fatigue. The system does not need to be fancy, it just needs to fit the way the office actually works.
That is especially true for small professional teams in Cape Town, Durban, Pretoria or Gqeberha. The details change from place to place, but the need is the same: protect client information, keep staff moving and make sure the right people have the right access at the right time.
Key facts
| Client type | Accounting office |
|---|---|
| Town | Salt River, Cape Town |
| Team size | 40 staff |
| Timeline | 3 weeks |
| Core services | Initial Security Review, Platform Setup, SSO Configuration, Vault Structure Design, Permission Mapping |
| Key outcome | Role-based access with stronger login hygiene and clearer offboarding |
