The Claremont brief and who was involved
The client was a property management team in Claremont, Cape Town, with agents, office administrators and support staff all needing access to the same set of cloud tools. The ask was straightforward on paper: make logins easier on phones and laptops, cut down on shared passwords and give management better control over who could see what.
They were working in a busy local market where staff were often out on viewings, handling queries from the office and checking records after hours. That meant access had to work properly on mobile devices, whether someone was in Claremont, Bellville or working from home during load-shedding.
The constraints we had to plan around
The biggest constraint was that the team could not afford a messy rollout. Several people were using different sign-in habits already, and a few critical systems were tied to older passwords that had to be handled carefully. We also had to keep disruption low because the office still had to keep trading while the changeover happened.
- Mixed device use: phones, laptops and shared office computers
- Limited time for training during office hours
- Staff moving between site visits and remote work
- Need for tighter control over leavers and temporary access
- Practical use during outages and patchy connectivity
There was also a clear security concern around staff turnover and temporary project access. The team wanted one place to manage credentials rather than relying on notes, reused passwords or informal handovers that can cause trouble later.
What 1Pass supplied and set up
We put together a simple access structure that matched the way the estate office actually worked. That started with an initial security review, then a clean vault structure design for departments, agents and management. From there, we mapped permissions so each person only saw the applications and records needed for their role.
The rollout also included SSO configuration for the main business tools, password migration from the old setup and user onboarding training for the whole team. For staff who handled admin changes, we added a separate admin training session so they could manage joins, moves and leavers without needing support for every small update.
- Initial Security Review
- Platform Setup
- SSO Configuration
- Vault Structure Design
- Permission Mapping
- User Onboarding Training
- Admin Training
- Password Migration
Our technical support lead also stayed involved during the switch-over, which helped the team get through first login issues quickly. That mattered because even small delays can slow a property office down when showings and client calls are coming in back to back.
Four week rollout from review to live use
The project ran over four weeks from first review to full adoption. Week one covered the security review and planning, week two covered setup and SSO configuration, week three handled migration and staff training, and week four was for support, fixes and final sign-off. That pace worked well for a team that could not stop normal operations.
We kept the process remote where possible, with short check-ins instead of long meetings. That made it easier for staff to join from the office, from home or between appointments. The final result was a cleaner system that was live quickly, but still had enough structure behind it to be managed properly over time.
Results for the estate office team
After rollout, the team had fewer password resets, less confusion around shared access and a much clearer process for bringing new staff in or removing access when someone left. Agents could get to the systems they needed from a phone or laptop without chasing codes or waiting on office staff to unlock accounts.
For management, the biggest win was control. They could see who had access, keep permissions tidy and reduce the risk that old credentials would hang around. In practical terms, that meant less admin work, better security and fewer interruptions during a normal working day.
- Faster access for field agents and support staff
- Less reliance on shared passwords
- Clearer offboarding and permission control
- Better day to day admin for office staff
- Improved consistency across mobile and benchtop use
The team also found it easier to keep working during power cuts and while staff were away from the office. Because the login process was simpler, they spent less time sorting access and more time on client work, which is what the office needed most.
What we learnt from this office rollout
We would take the same approach again for any small property team that needs secure access without making the office slower. Start with the actual roles, map permissions before migration and give admins a practical handover so they can manage the system confidently after go-live.
For offices in Cape Town, Johannesburg or Durban, that local timing matters too. A rollout has to fit around show days, calls, school runs and load-shedding, not the other way round. In this case, the plan held up because it was built around how the team already worked, not how a generic system expects them to work.
If we were repeating this project tomorrow, we would keep the same focus on short training sessions, clean access groups and a final review after the first few weeks. That is usually where small issues show themselves, and it is the best time to sort them properly.
Key facts
| Client type | Property management office |
|---|---|
| Location | Claremont, Cape Town |
| Timeline | 4 weeks |
| Scope | Password manager and single sign-on rollout for agents and support staff |
| Delivery | Remote onboarding with admin and user training |
| Key result | Cleaner access control and fewer password-related interruptions |
