Start With A Simple Map Of Who Needs Access
Before you create folders or groups, list the people who use passwords every day and the systems they need. Keep it practical. A bookkeeping user in Johannesburg does not need the same access as a field supervisor in Durban or a sales rep working remotely from Stellenbosch.
Start with roles, not names. That makes it easier to manage staff changes, annual leave and new appointments without rebuilding the whole vault. If one person handles payroll, client portals and supplier logins, split those into separate access sets so the risk stays controlled.
- Write down each role in the business
- List the apps and systems tied to that role
- Mark which logins are shared and which must stay private
- Note any compliance or client requirements
Group Systems By Function, Not By Department Only
A clean vault structure works best when it follows how people actually use the tools. Group systems by function such as finance, operations, customer support, marketing and admin. Then add subgroups where needed, for example supplier portals, payroll systems, social accounts or municipal service accounts.
This helps during load-shedding too. If someone needs to log in quickly from a laptop hotspot or mobile data, they should know exactly where to go without searching through a long list. In Cape Town, Pretoria or Gqeberha, a simple structure also helps when staff are working from the office one day and home the next.
Keep the names short and consistent. Use plain labels that any team member can understand at first glance.
- Finance and payroll
- Operations and logistics
- Client systems and portals
- Marketing and content tools
- Shared admin accounts
Set Permissions So People Only See What They Need
Permission mapping is the part that keeps the vault safe. Each group should only see the passwords required for its work. If everyone can see everything, the structure is neat on paper but weak in practice.
A practical rule is to give direct access to the smallest number of people needed for the job. A manager may need read access for oversight, while a specialist may need full access to update records or move logins between folders. If a contractor is brought in for one month, give temporary access and review it before the job ends.
Check permissions whenever someone changes role, leaves the business or starts working on a new account. Small teams often miss this step when things are busy, and that is where mistakes creep in.
- Limit each group to the relevant systems only
- Use separate access for admins and standard users
- Remove temporary access once the work is done
- Review shared accounts after any staff change
Use Naming Rules That Stay Clear Six Months Later
Vault names, group names and item names should all follow one pattern. Pick a format and stick to it. For example: department, system type, then purpose. That way a login created today will still make sense when someone else needs it next quarter.
Avoid vague labels like "old login" or "main account". Those cause confusion during handovers, especially in small businesses where one person may manage many systems. Include location only where it matters, such as branch-specific supplier or municipal accounts. If the same tool is used across branches, keep it central and do not duplicate it across folders.
Good naming also helps during monthly checks and quarterly access reviews. The team can scan the list and spot entries that are out of date, duplicated or no longer in use.
Plan For Onboarding, Offboarding And Team Changes
A vault structure is not finished when it is created. It must support the full staff cycle. New users need the right folders from day one, while exiting staff should lose access cleanly and without delay. That is especially important when people share tasks across branches or work remotely nationwide.
Build a simple handover process into the structure. When someone joins, assign the correct group, confirm their training and show them where to find passwords and notes. When someone leaves, remove access, check any shared logins and update recovery details. If one person held several admin roles, separate those roles before you close their access.
For small businesses in South Africa, this is often where a bit of planning saves a lot of trouble later.
- Define a new user checklist
- Define a leaver checklist
- List who approves access changes
- Record any shared account updates after staff changes
Check The Structure Against Daily Use
Once the vault is set up, test it with real work. Ask a finance user, an operations user and an admin to find the items they use most. If they need more than a few clicks, the structure probably needs tightening.
Watch for folders that are too broad, duplicate items, or permissions that have been copied instead of planned. A good structure should feel boring in the best way: easy to follow, quick to update and clear during pressure moments like month-end, payroll cut-off or a supplier payment run.
It also helps to set a review date. Quarterly works well for most small teams. That gives you time to catch stale access, tidy labels and keep the vault aligned with the business as it changes.
- Can staff find common logins quickly
- Are folders grouped by real working needs
- Do permissions match current roles
- Are old accounts removed or archived
A Practical Checklist Before You Go Live
Before you roll the vault out to the full team, run through a final check. This does not need to be complicated. It just needs to be consistent. A short review now is far better than fixing confusion later when staff are already using the system every day.
Make sure the structure is easy to explain to new users, that admin access is limited, and that shared folders are clearly marked. If your team works across Woodstock, Johannesburg, Durban or remote sites, keep the setup simple enough for someone to follow from anywhere with a stable connection.
- Folder names are clear and consistent
- Groups match job roles and not just names
- Shared accounts are marked and controlled
- Admin access is limited to the right people
- New user and leaver steps are documented
Once these basics are in place, your vault becomes easier to manage and much less stressful for the team.
