What the Durban team needed from the start
The client was a growing ecommerce business in Durban with staff split between customer support, fulfilment, marketing and admin. They had too many shared logins, a few old accounts still active and no consistent way to handle access when a person joined, moved roles or left.
The brief was clear: reduce risk, make access easier for the team and stop time being lost on password resets during busy trading periods. They also wanted a setup that could work for remote staff and for the people handling orders on site, without making daily work slower.
- Secure access for store, support and fulfilment accounts
- Group based permissions for different job roles
- Simple onboarding for new starters
- Cleaner offboarding when staff changed roles or left
- Remote support that did not interrupt operations
Constraints on the ground in Durban
Like many ecommerce teams, they were working around shift changes, shared devices and urgent customer queries. Load-shedding meant staff could not rely on long manual processes, and the team needed a system that was quick to use even when power or connectivity was patchy. A few older accounts also had weak recovery details, so part of the job was tightening that up before the rollout went wider.
We also had to keep the process practical for a team that was already busy picking, packing and answering customer messages. No long downtime, no confusing steps, and no gap between setup and real use.
- Some users were on benchtop in the office, others were remote
- Several accounts had been shared informally for months
- Access levels differed by department and shift
- Training had to be short enough to fit around peak order times
How we structured the access rollout
We started with an initial security review and mapped every account by function. From there we designed vault structure, permission groups and the admin workflow so the business could see who had access to what at a glance. The aim was to keep the setup tidy from the start, not patch it later.
We then carried out password migration for the main business tools and set up single sign-on where it made sense. This cut down on repeated logins and made it easier for staff to move between the systems they used every day, from order handling to internal communication tools.
- Vaults separated by department and sensitivity
- Role based permissions for office, support and fulfilment staff
- Admin access limited to the people who actually needed it
- Clear naming structure for shared and individual accounts
Implementation details that mattered
The setup was completed over three weeks in stages so the business could keep working while changes were made. Week one covered discovery, account review and structure planning. Week two covered configuration, migration and testing. Week three focused on user onboarding training, admin training and final checks with the team.
We kept the workflow simple. Staff received only the access they needed, and the admin team got a process for adding, changing and removing access without guesswork. That included a cleaner offboarding process so old logins would not hang around longer than they should.
- 3 week rollout from review to handover
- Group permissions aligned to department duties
- Remote onboarding for staff outside Durban when needed
- Quarterly access reviews planned for ongoing control
What changed after go live
Once the setup was in place, the business had better control over who could reach the important accounts. The support team no longer had to chase passwords during busy hours, and fulfilment staff could get to the tools they needed without relying on a shared notebook or a colleague being available.
The biggest gain was time. Managers had a clearer view of access, staff knew where to find what they needed and the handover process became much neater. It also reduced the chance of an old account being left active after a role change, which is a common weak point in small teams.
- Less time lost to login problems
- Cleaner control over shared business accounts
- Faster onboarding for new staff
- Stronger offboarding when people moved on
What we would repeat on the next Durban rollout
If we were doing the same kind of setup again for another Durban ecommerce team, we would use the same order: review first, structure second, migration third and training last. That sequence gives the business a chance to see how the setup will work before everything is switched over, and it keeps disruption low.
We would also keep the admin group tight from the start, especially where order volumes are high and staff changes happen often. In a busy ecommerce operation, the strongest setup is the one that stays easy to manage after the first month, not just on launch day.
- Start with an access audit before moving any passwords
- Keep department groups narrow and easy to understand
- Train the admin users separately from general staff
- Plan quarterly reviews into the calendar from day one
Key facts
| Client type | Durban ecommerce business with store, support and fulfilment teams |
|---|---|
| Project scope | Password management, single sign-on, permissions and onboarding |
| Timeline | 3 weeks from review to handover |
| Core work | Initial Security Review, Platform Setup, SSO Configuration, Password Migration |
| Access model | Group permissions by department and role |
| Support model | Remote onboarding, admin training and quarterly access reviews |
