Shared access without shared risk
In a school or training centre, there are usually many people who need access to the same systems: learner records, timetabling, finance, learning platforms, printing portals and assessment tools. That often leads to passwords being written on paper, copied into group chats or reused across accounts. It saves time in the moment, but it creates gaps when a staff member leaves, a temp fills in, or a password gets passed from one person to another without proper control.
1Pass is suited to this kind of environment because it keeps access organised by role rather than by memory. A principal, admin assistant, facilitator or IT support person can have access to what they need, while sensitive accounts stay restricted. For schools in Cape Town, Johannesburg, Pretoria, Durban and Gqeberha, that means fewer access headaches and less time spent resetting accounts after hours. It also helps when load-shedding interrupts the day and staff need to log back in quickly on shared devices. It is one less thing to worry about.
What a typical school setup looks like
Most schools and training teams do not need complicated hardware for this to work. They usually already have a mix of laptops, benchtop computers, tablets, printers, learner management systems and a few shared devices in reception or admin. In some cases there are also biometric clocks, Wi-Fi admin logins, cloud storage, payroll access and online exam tools. The important part is not the device count, it is how those logins are structured.
- Admin office computers used by several staff members
- Shared tablets or laptops for teaching and training rooms
- One or two central accounts for finance, payroll and communications
- Role-based access for educators, facilitators and support staff
- Remote access for managers who work across more than one site
We usually suggest starting with the highest-risk accounts first: admin, finance, learner records, and any platform that manages user permissions. After that, the rest of the organisation can be added in phases. This keeps the rollout manageable and limits disruption during term time or busy registration periods.
Planning the rollout around your term calendar
Schools and training centres work best with a rollout plan that avoids registration week, exams and major reporting deadlines. A good setup starts with an initial security review, then platform setup, vault structure design and permission mapping. After that comes user onboarding training for day-to-day staff and admin training for the people who manage accounts. If needed, password migration can be handled in batches so the work is not all done in one sitting.
For multi-campus institutions, it helps to map access by site first, then by team. For example, a head office in Woodstock may need different access from a training site in Stellenbosch or Century City, while support staff in Pretoria or Durban may only need limited permissions. The same applies to remote onboarding nationwide. You do not want one shared login for everything because that becomes messy fast and one person can end up locked out of the whole system.
- List every shared system and who uses it
- Decide which accounts need admin control only
- Separate staff access from learner access
- Plan training before the busiest week of the term
- Keep a clear offboarding process for staff who leave
Common mistakes that cause access problems
The most common problem is leaving access to memory. A second mistake is giving too many people the same login because it feels easier at the start. That leads to confusion later when there is no audit trail and no one can tell who changed what. Another issue is not updating access when a teacher, tutor or administrator moves roles. A password can stay active for months after it should have been removed.
We also see schools leave important accounts tied to one person only. If that person is sick, on leave or no longer with the school, the whole team slows down. In coastal towns like Gqeberha or Durban, humidity and older equipment can also make shared devices less reliable if logins are not simple and well recorded. A clear system helps cut down on these delays, especially when staff are already juggling classes, admin and parent queries. It is simple work, but it makes a big difference.
Budget ranges for smaller teams and larger campuses
Budget usually depends on team size, the number of shared systems and how much support is needed during rollout. A small training centre with one office and a few facilitators will cost less than a school with several admin users, multiple campuses and offboarding controls for seasonal staff. As a guide, many smaller teams start from about R 1,500 to R 3,500 for initial setup support and basic configuration. Larger campuses, multi-site schools and more involved migration projects can range from R 5,000 to R 15,000 or more, depending on the number of accounts and training sessions.
Ongoing support and quarterly access reviews are worth planning for as well, especially where staff changes are common. If you are managing admissions, short courses or part-time trainers, that regular review keeps access tidy and reduces risk. A bit of structure upfront often costs less than one major lockout later.
- Small team setup: from R 1,500 to R 3,500
- Multi-user rollout: from R 5,000 to R 15,000+
- Quarterly access reviews: best planned as an ongoing line item
- Training and migration: budget extra if there are many shared accounts
Support for administrators, educators and support staff
1Pass is built for teams that need practical access control, not extra admin. The system can be set up so administrators manage permissions, educators access teaching tools, and support staff handle only the systems they need for day-to-day work. That makes handovers easier at the end of a term, when staff are on leave or when a contractor fills in for a few weeks.
Our team in Woodstock supports schools and training centres across South Africa, including Johannesburg, Pretoria, Durban, Gqeberha and remote sites nationwide. Lukhanyo Maseko leads the business, with support from Siyanda Mdletshe, Revasha Moodley, Kgosi Kgosana, Ruan van der Merwe, Zinhle Khumalo and Zaheer Davids. If your institution needs safer shared access, structured onboarding and a clear offboarding process, the setup can be planned around your school calendar and your available staff time.
