Midrand team brief and what needed fixing
The client was a small professional services team in Midrand with staff working from home across South Africa, including Johannesburg, Pretoria, Durban and a few coastal areas where laptops and internet connections can be a bit inconsistent. Their day-to-day problem was simple enough on paper but messy in practice: too many shared passwords, too many browser saves, and no one clear process for new starters, leavers or temporary access. We were asked to put proper control around sign-ins without slowing people down.
The team needed a setup that would suit non-technical users, support remote onboarding and still give management a clear view of who had access to what. They also wanted to reduce risk during load-shedding, when people tend to reconnect on different devices and sometimes use fallback links or personal phones. That meant the access process had to be practical, not fussy.
- Client type: small distributed office team
- Base area: Midrand, with remote users nationwide
- Main need: secure password sharing and single sign-on
- Working pattern: home-based staff, mixed devices, frequent user changes
Security review before any setup work
We started with an initial security review to understand where passwords were stored, which applications were in use and where the biggest access risks sat. The team used a mix of cloud tools, finance systems, communication apps and internal admin platforms. Some accounts were still being shared in message threads or on personal notes, which is common enough in smaller businesses but it does not hold up well once a team grows past a handful of people.
We mapped the current state, identified duplicate accounts and flagged places where access should have been role-based instead of shared. The aim was not to over-complicate things. It was to get the business to a place where staff could reach the tools they needed, while management could remove access quickly when someone changed role or left. That matters for any team, but especially one with remote staff spread across provinces.
- Reviewed current password handling and account ownership
- Checked which apps needed single sign-on
- Identified shared accounts and orphaned logins
- Set a clean access model for staff, managers and admins
Platform setup for remote users across South Africa
Once the review was done, we carried out the platform setup and built the password vault structure around how the team actually works. Shared logins were grouped by department and function, with separate access for admin, finance and operations. That gave the team a clear structure instead of one long list of passwords that everyone could see. We also set up single sign-on for the key applications so staff could move between tools without constantly resetting or retyping credentials.
Because the team had users in Johannesburg, Pretoria, Durban and Gqeberha, we kept the rollout remote and light on admin. Users received step-by-step onboarding support and the main administrators were shown how to approve access, update records and manage permission changes without needing support for every small adjustment. The setup worked well for mixed internet conditions and it did not depend on anyone being in the same office on the same day.
- Vault structure designed for departments and access levels
- SSO configured for core business applications
- Permission mapping set for each role
- Remote onboarding completed for users in multiple towns and cities
Migration, training and handover in four weeks
The full project ran over four weeks. Week one covered review and planning, week two focused on the vault build and permissions, week three was for password migration and user onboarding, and week four was used for admin training, testing and final adjustments. That pace suited the client because they wanted a controlled changeover without stopping normal work. No one had time for a long interruption and honestly most small businesses do not.
We migrated priority passwords first, then moved lower-risk items once the team was comfortable. Training was split between regular users and administrators so each group got only what they needed. Staff learned how to sign in, find shared credentials and avoid storing passwords in unsafe places. Admins got the practical side: onboarding, offboarding, permission changes and quarterly reviews. A few users needed extra help at the start, especially those juggling work between home internet and mobile data, but the support process was straightforward.
- Timeline: 4 weeks from review to handover
- Priority migration first, then full password transfer
- User and admin training delivered separately
- Remote support provided throughout the rollout
What changed after go-live
After go-live, the team had one central place for credentials and a much clearer process for access. New starters could be set up faster, and when someone moved roles or left the business, access could be removed without hunting through old notes or asking around the office. That alone saved time and reduced risk. It also made audits and internal checks easier because the business could see who had access to what.
From a staff point of view, the day-to-day experience improved too. People were not wasting time trying to remember old passwords or waiting for a colleague to send over a login. Single sign-on cut the number of repeated sign-ins, which is useful when staff are moving between apps all day. The result was less admin friction and fewer avoidable access issues during busy periods and power cuts.
- Faster onboarding and offboarding
- Less password sharing through informal channels
- Clearer access control for admins and managers
- Reduced login delays for remote staff
What we would repeat on the next remote rollout
If we were doing the same type of rollout again for another Midrand team or a business with staff spread between Gauteng, the coast and home offices, we would follow the same order: review first, permissions second, migration third, then training and support. That sequence gives everyone a proper picture of the risks before anything is moved and keeps the change manageable. It also helps avoid the common mistake of setting up tools before agreeing who should actually have access.
The other thing we would repeat is keeping the admin model simple. Small businesses do not need layers of complexity to stay secure. They need a process that is clear, consistent and easy to follow when people are busy, travelling or working through load-shedding. That is where 1Pass fitted this project well: practical structure, controlled access and support that matched the pace of the team.
- Start with a security review, not a rushed login migration
- Keep admin roles simple and well documented
- Train users and admins separately
- Plan for remote work, power cuts and mixed device use
Key facts
| Project location | Midrand, with remote users nationwide |
|---|---|
| Client type | Small distributed business team |
| Timeline | 4 weeks |
| Core services | Initial Security Review, Platform Setup, SSO Configuration, Vault Structure Design, Permission Mapping, User Onboarding Training, Password Migration, Offboarding Process Design |
| Team involved | Lukhanyo Maseko, Siyanda Mdletshe, Revasha Moodley, Kgosi Kgosana, Ruan van der Merwe, Zinhle Khumalo, Zaheer Davids |
| Outcome | Centralised password control, simpler onboarding, faster offboarding and cleaner access for home-based staff |
