What Platform Setup Covers for Small Teams
Platform Setup is the foundation of a clean 1Pass rollout. We configure the core structure of your environment so it matches how your business actually works, not just how the software is laid out by default. That means users are grouped properly, access rules are mapped to roles, and the vault structure supports daily work from the first login.
For small businesses in Johannesburg, Pretoria, Durban, Gqeberha and Cape Town, a tidy setup saves time later when staff join, change roles, or leave. It also helps reduce password sharing across WhatsApp chats and sticky notes on monitors, which is still too common in offices running under load-shedding pressure and busy week to week operations.
- User and admin role setup
- Group creation and permission planning
- Vault structure aligned to departments or functions
- Policy settings for access control and sharing
- Initial configuration for remote teams and multi-office use
How We Structure Users, Groups and Permissions
We start by looking at your team size, department split and who needs access to what. A 12 person accounting firm in Woodstock will need a different structure to a 40 user sales team spread across Durban and Pretoria. We build the setup around actual working patterns, so users see only the information they need and admins can keep track of who has what access, even when staff move fast.
Our process normally includes group design for teams such as directors, finance, operations, sales and support. We also map permission levels for standard users, team leads and system administrators. If your business uses contractors or seasonal staff, we include those access rules too so they are easy to remove later.
- Role-based access mapping
- Department or project based group design
- Shared vault structure for teams and business units
- Restricted access for sensitive logins and admin accounts
- Clear naming rules so staff can find items quickly
Setup Steps From Review to Go-Live
Most Platform Setup work follows a simple sequence. First, we review your current state, including how many users you have, which applications need to be brought in, and where the risks sit. Then we build the structure in 1Pass, test the access flow, and prepare the rollout notes for your internal team.
We prefer to keep the steps practical and short. In many cases, setup can begin as soon as your team list and app inventory are confirmed. For businesses with offices in different towns or staff working from home, we can handle the setup remotely and coordinate with your internal contact during business hours. There is no need for long meetings if your admin information is already organised.
- Step 1: Review users, departments and application list
- Step 2: Build groups, vaults and admin structure
- Step 3: Apply permissions and sharing rules
- Step 4: Test access and make adjustments
- Step 5: Hand over setup notes and next steps
Typical Turnaround and What Affects It
Turnaround depends on the number of users, the number of systems you want included, and how prepared your records are. A small team with clear staff details and a short application list can often be set up within a few working days. Larger rollouts, or businesses with multiple branches and historical access issues, usually take longer because each rule needs to be checked carefully.
Things that can slow the process include incomplete user lists, unclear ownership of shared accounts, and last minute changes to who should receive admin rights. If your business has staff in different provinces or uses a mix of office and remote workers, we also factor in coordination time so the rollout is not rushed. That keeps the setup clean and easier to maintain over the long term.
Key facts
| Base location | Woodstock, Cape Town |
|---|---|
| Service area | Johannesburg, Pretoria, Durban, Gqeberha and nationwide remote onboarding |
| Turnaround | Typically a few working days for small teams, longer for larger or multi-site rollouts |
| Pricing approach | Quoted to team size, complexity and number of systems to configure |
| Maintenance interval | Quarterly access review recommended, with adjustments after staff changes or role changes |
