Sandton sales logins under control
The office was a small but active sales operation in Sandton with people moving between CRM, quoting tools, shared folders and internal systems from 8 am to late afternoon. Every rep had a long list of logins and the same people were wasting time on password resets, account lockouts and copy-pasted credentials saved in unsecured places. In a sales floor, even a few minutes lost between calls adds up fast.
The brief was simple enough on paper: reduce repeated logins, make access easier for the team and keep control in the hands of one admin group. They also wanted a setup that could be managed remotely because the team was partly hybrid and not everyone was in the office each day. Their concern was not just convenience, it was the mess that can happen when staff leave, roles change or someone shares a password over chat without thinking.
Project constraints that shaped the rollout
We started with an initial security review and mapped the applications already in use, including the ones with older authentication settings. The main constraint was keeping the changeover low friction. Sales staff cannot afford a long system interruption, and the team needed to keep working while the new login process was introduced. Another limit was mixed device use, with some staff on office machines and others working from laptops at home or between client meetings.
There was also a practical load-shedding concern. Some users had limited battery backup and unstable connectivity during interruptions, so the onboarding had to be staged in a way that did not depend on everyone being online at once. We kept the admin controls straightforward, because a complicated setup usually gets ignored after week one. The office wanted security that fit the pace of real work, not a layer of admin that slows people down.
- Town focus: Sandton, Johannesburg
- Team size: small sales office with shared access needs
- Rollout style: remote-first with on-site style support by screen share
- Priority: reduce repeated logins and admin time
What we supplied and set up
We handled the platform setup, single sign-on configuration and vault structure design, then mapped permissions so each person only saw what they needed for their role. That meant sales reps got quick access to the apps they used every day, while managers and admin users had the control functions needed for approvals, user changes and quarterly access checks. We also set up password migration so existing credentials were moved into the vault in a controlled way instead of being left scattered across browsers and notes.
To keep the handover practical, we ran user onboarding training and admin training separately. The team did not need a long theory session, they needed to know where to log in, how to reset access and what to do if a new starter joined on a Monday morning. We also designed the offboarding process so when someone leaves, access can be removed in one clear sequence. That matters in sales where staff turnover can be higher than people expect.
- Initial Security Review
- Platform Setup
- SSO Configuration
- Vault Structure Design
- Permission Mapping
- Password Migration
The implementation timeline
The project ran over three weeks from first review to full handover. Week 1 covered discovery, system mapping and the permission plan. Week 2 was the setup phase, where we configured SSO, built the vault structure and tested login flows with the key applications. Week 3 focused on training, migration and final checks with the admin team. We kept the pace steady so the office could absorb the changes without losing a sales day.
Because the team was in Johannesburg but support could be handled remotely from our Cape Town base, we scheduled short sessions at practical times. That reduced disruption and allowed us to test the setup with the real people who would use it daily. A few users needed extra help with browser settings and MFA prompts, which is normal on a first rollout, and we sorted those issues before the go-live was declared complete.
Results for the sales office
Once the new setup was live, the team stopped jumping between repeated logins and a lot of the small delays disappeared. Reps could move from one application to the next with far fewer interruptions, and managers had a clearer picture of who had access to what. The office also had a single process for new starters and leavers, which made the admin side far less messy.
There was a noticeable drop in password-related support requests, especially around forgotten credentials and account access after device changes. The staff did not need to remember as many separate passwords and the whole team got a more controlled way to handle logins. For a sales environment, that translates into more time spent on calls, quotes and follow-ups instead of waiting for access to work again.
- Fewer repeated logins across core applications
- Cleaner user access control for active staff and leavers
- Less time lost to password resets and account lockouts
- Simple admin handover for ongoing team changes
What we would do again for a similar team
For another Sandton office, or any similar sales team in Johannesburg, we would use the same approach: review first, then permissions, then controlled rollout and training. That order keeps the process manageable and avoids a rushed launch that leaves the admin side guessing. We would also keep the offboarding sequence and quarterly access review in place from day one, because access control only works if somebody keeps checking it.
If the office had more remote staff or a second branch, we would still use the same method but with a tighter rollout schedule and more time spent on support during the first fortnight. Small teams do best when the setup matches the way they actually work, not an idealised version of it. That was the value here, and it is the part we would repeat without changing much.
- Keep onboarding short and role-based
- Test login flows before full rollout
- Train admins separately from end users
- Build offboarding and quarterly reviews into the process from the start
Key facts
| Project location | Sandton, Johannesburg |
|---|---|
| Client type | Small sales office |
| Timeline | 3 weeks |
| Core setup | Single sign-on, password vault and permission mapping |
| Support model | Remote onboarding and admin training |
| Outcome | Fewer repeated logins and clearer access control |
