Create and update accounts
Create learner and staff accounts, update details and record email addresses back in Hero.
Built for schools using Hero
Keep Hero, Google and your cloud platforms in sync automatically.
AUTO-OPS Cloud User Sync manages student and staff account changes from enrolment through to leaving — including Google accounts, organisational units, Hāpara sync and Google licence clean-up.
For school admin, IT and leadership teams who want fewer spreadsheets and cleaner cloud access.
Cloud user lifecycle
1Hero changesNew, updated, moved or leaving users
2AUTO-OPS applies your rulesAccounts, OUs, groups and sync tasks
3Cloud access stays alignedGoogle, Microsoft 365, Hāpara and Apple
The problem
A simple change in Hero can still create work in three or four other systems.
When a learner enrols, changes class, moves groups or leaves, someone often needs to update Google Workspace, Hāpara, Microsoft 365 or Apple School Manager as well.
That means spreadsheets, manual checks, delayed access and a higher chance of old accounts, wrong OUs or licences being left behind.
What AUTO-OPS handles
User lifecycle automation from Hero.
AUTO-OPS Cloud User Sync uses Hero as the source of truth, then carries out the cloud user changes your school would otherwise manage manually.
Place users in the right Google OUs
Move users into the correct organisational units as their role, year level or status changes.
Manage Google licence clean-up
Help avoid licences being left behind when users move between OUs where licence rules are not configured.
Sync with Hāpara
Keep learner and class information aligned so teaching teams have access to the right groups.
Support leavers and transitions
Move leaving students into the right status or organisation so access is easier to control.
Report on changes
Give your team a clearer view of what changed, when it changed and what AUTO-OPS processed.
New improvement
Avoid forgotten Google licences when users move OUs.
In Google Workspace, a user moved from one organisational unit to another may keep a licence if the new OU does not have licence rules configured to remove it.
AUTO-OPS Cloud User Sync helps manage this as part of the wider lifecycle process, so schools have better control over accounts, OUs and cloud access as users move through the school.
Useful when users are:
- Enrolling or starting at the school
- Changing class, group or status
- Moving between Google OUs
- Leaving the school
- Needing cloud access reviewed
Connected platforms
Synchronise your school systems without spreadsheet workarounds.
“The creation of an automated process that creates our learner emails and updates our SMS (Hero) and core cloud platforms (Google and like Hāpara Dashboard) for us is invaluable! No more lost time creating endless spreadsheets to handle the data and creation process.”
Kent Somerville, Associate Principal, Pt England School
How it works
A managed service, not another job for your team.
Connect Hero and your cloud platforms
Craig and the RCG Creations team help set up the connection and confirm your school’s rules.
AUTO-OPS runs the lifecycle tasks
When Hero data changes, AUTO-OPS creates, updates, moves or syncs users based on your setup.
Your team gets time back
Reduce manual admin, improve consistency and give staff more confidence that cloud access is up to date.
Get the details
Download the AUTO-OPS Cloud User Sync Info Pack.
The info pack explains what AUTO-OPS does, how it works with Hero and cloud platforms, pricing guidance and how to get started.
Inside you’ll find:
• Supported lifecycle tasks
• Platform sync overview
• Google OU and licence management notes
• Onboarding steps
• Pricing and next steps
Want to check if it fits your school?
Book a 30-minute walkthrough with Craig.
Talk through your Hero setup, Google OUs, current manual tasks and where AUTO-OPS could save your team time.
