What permission mapping covers for your team
We start by mapping who does what in your business, then we line that up with the systems your staff use every day. That means sales, finance, operations, HR, project teams and directors each get access matched to their actual duties, not a guess made in a hurry. It is practical work, and it helps prevent shared logins, over permissioned accounts and awkward clean-up later on.
For South African small businesses, this matters most where teams change quickly, staff work across branches, and some people need access from home or on the road. We set the structure so a person can see the right folders, apps and records, while sensitive items stay locked down. We also keep an eye on load-shedding realities and remote access habits, because weak permission habits often show up when people are rushing to work around power cuts.
- Role based access for daily users, managers and admins
- Separate access for finance, HR, operations and leadership
- Restricted permissions for sensitive customer and supplier data
- Clear rules for shared resources, vaults and application groups
How we build the access model
We begin with a short review of your current team structure, your apps and any existing password or sign-on process. Then we group tasks by responsibility, not by title alone, because in small teams one person may handle stock, invoices and client support over the course of a week. That is where the detail matters. A receptionist in one office may need different access from a branch coordinator in another office, and the permissions should reflect that.
We then create a permission map that shows which users, teams and admin roles can enter each system. This includes who can view, edit, approve, reset, invite or remove users. If you already have a list of applications, we use it to reduce duplication and tidy up access that no longer makes sense. It is a straightforward process, but it saves a lot of back-and-forth later.
- Current access review
- Role and department grouping
- Application by application mapping
- Approval and escalation rules
What is included in the service
The service is built for teams that want a clear, workable setup without spending weeks trying to figure it out internally. We set the permissions structure, document the decisions and make sure the admin side is easy to maintain. If your business has staff in Woodstock, Century City, Stellenbosch, Johannesburg, Pretoria, Durban or Gqeberha, we keep the model consistent across sites while still allowing local variation where it is needed.
You also get practical handover support so your team understands what each role can do and why. That includes guidance for access changes when someone joins, moves roles or leaves. We also help you avoid the common trap of giving admin rights to everyone because it feels quicker on a busy Monday. That sort of shortcut usually causes more work later. Sometimes a business needs 2 or 3 admin users, not 12.
- Permission mapping workshop with your team leads
- Draft access structure and review cycle
- Admin guidance for updates and approvals
- Offboarding access rules for leavers and contractors
Turnaround and rollout timing
Most permission mapping projects can be completed in a few working days once we have the right information from your side. Smaller teams with a limited number of apps are usually quicker, while businesses with multiple branches, shared systems or layered approvals may take longer. We work remotely nationwide, so your team does not need to be in the same room, which helps if you are spread between Cape Town and Gauteng or working hybrid across several locations.
We will give you a clear timeline before we start, including when we need input from your managers and when review points will happen. If your rollout is tied to a staff intake, a new system or year end cleanup, we can plan around that. For many businesses the biggest time saver is simply getting the structure right before access is handed out. It cuts down on rework and avoids last minute panic.
Pricing approach and what affects cost
Pricing is based on the size of your team, the number of applications, the number of permission levels needed and how much cleanup is required on the current setup. A business with 8 users and a simple app stack will not need the same effort as a 60 user team with finance approvals, branch access and contractor accounts. We keep the pricing practical and transparent, and we explain what is included before any work starts.
If your access structure is already fairly tidy, the work is lighter. If you have duplicate accounts, old staff entries or several people sharing one login, we spend more time getting the map right. That is normal. We do not charge for noise, only for the work needed to produce a clean permissions structure that your team can actually use.
- Priced according to team size and app count
- Higher complexity for approvals and multiple branches
- Optional support for migration and clean-up work
- Clear scope before implementation starts
Keeping permissions current after go live
Permission mapping should not be treated as a once off task. Teams change, projects end, contractors leave and new tools get added. We recommend quarterly access reviews for most small businesses, with faster checks after staff changes or system upgrades. In a busy office, especially where people wear more than one hat, these reviews catch access drift before it becomes a problem.
We can also help you set a simple maintenance rhythm: monthly checks for new starters and leavers, plus a fuller quarterly review of admin rights, shared access and sensitive groups. That keeps the setup current without burdening your managers. It also makes audits and internal checks much easier. In our experience, a short review done on time is worth more than a big clean-up done in a rush.
- Monthly joiner mover leaver checks
- Quarterly access reviews for all active users
- Admin rights review after staff or system changes
- Support for ongoing updates and access questions
Key facts
| Service area | Woodstock, Cape Town and nationwide remote support |
|---|---|
| Typical team size | Small business teams from 5 to 100 users |
| Turnaround | Usually a few working days, depending on complexity |
| Delivery method | Remote onboarding with manager input and review points |
| Pricing model | Quoted by scope, user count and application complexity |
| Review interval | Quarterly access reviews recommended, with monthly joiner and leaver checks |
