GCgos
School iPad management, app deployment and class rosters, scattered across different screens, brought together in a web dashboard under one teacher account, and the same work by asking Claude. GCsoft sets up and runs the servers, so there's nothing for the school to install or maintain.
If your school already uses Argos MDM,
there's nothing new to adopt — it plugs right in on top.
Address: gcgos.gichansoft.com · For a demo, contact [email protected].
One place, no switching screens.
The Argos MDM console and Google Classroom each demand their own login and their own screen. Yet what a teacher actually wants — "apply a policy to the iPads of the students in this class" — means going back and forth. GCgos shrinks that path to one screen, and in Claude to one sentence.
If your school uses Argos MDM, you can start today
GCgos is not a replacement MDM. It takes the single Argos MDM admin account your school already has, as-is, and sits on top of it. No re-enrolling devices, no rebuilding policies. The devices and policies you see in the Argos MDM console today show up in GCgos as they are.
- 01GCsoft prepares the servers and school settings
- 02Enter your Argos MDM account and school
- 03Issue teacher accounts — done
Putting "who did it" back on commands sent from a shared account
A school usually has just one Argos MDM account. When everyone shares it, Argos's logs only say "the school did it," and what was sent, when, and by whom disappears. So in GCgos, each teacher signs in with their own account, and every command sent is recorded in our own audit log along with who ran it.
Irreversible commands are split by permission. Policy deployment, app deployment, sync, push, and reboot are open to any teacher. Wipe and OS updates are admin-only.
Pick by class, deploy on the spot
The unit is "the students sitting in that period," not the homeroom — because that's the unit policies actually apply to.
- Pick target devices straight from Google Classroom rosters
- Per-platform policy deployment (iOS, Android, ChromeOS)
- Deploy apps registered in Argos MDM to devices
- Sync, push (wake), and reboot
- Save frequently used device sets as quick groups
Search as you type
The full list is fetched once and filtered in the browser. One search box matches accounts, devices, and classes.
- Local filtering in milliseconds for 2,000 devices
- 20-second list cache plus request coalescing — one upstream call even when many open it at break time
- Falls back to server search only when nothing matches
- "As of N seconds ago" labels and 30-second auto-refresh make freshness visible
- Bypasses the cache right after deploy or sync to show the latest state
Accounts, devices, and commands sent
From adding users to rotating MDM credentials — all done on screen, without touching the server.
- Add users, assign admins, deactivate, reset passwords, and unlock PINs
- View trusted devices and revoke trust individually
- Audit log — logins, account changes, and policy deployments
- MDM change log — every request sent via the shared account, plus who ran it
- Change the Argos MDM account and school settings (connection verified before saving)
- Run irreversible commands such as wipe and OS update
From class roster to device
- Pick Choose target devices from a Classroom class, a quick group, or search
- Check Students without linked devices and devices on other platforms are shown as "N excluded," not hidden
- Deploy Deploy a policy or app. Who ran it and the targets are recorded in the audit log
- Result The server decides whether it was accepted. Success shows a request ID; failure shows as failure
Wipes are double-checked
You must confirm the serial on screen and type it in to send. At the moment of sending, the server re-reads the list to compare, and won't send if anything differs.
Student ID: the bridge between students and devices
There's no common key between Classroom email addresses and device records, so we link them by student ID. Students with the same name are never auto-linked, and unlinked students stay visible on the roster.
Why a short PIN is safe
The device cookie itself is the second factor. PINs don't work outside trusted devices; 5 wrong tries lock for 15 minutes, and 10 revoke trust.
Google integration is read-only
Directory and Classroom access is read-only. GCgos cannot create classes or add or remove students.
Timetables and student search moved to School Helper
Comcigan timetables and student search are now a separate product, School Helper. GCgos focuses on Argos MDM, and together they let you pick targets with phrases like "period 3".
We provide the server
Run by GCsoft, with each school's data kept separate so it never mixes with other schools. No installing, updating, or backing up to worry about.
Schools on Argos MDM can start right away. To see it first, request a demo at [email protected].
Request a DemoThree screens to manage one class of iPads
The console is hard
The Argos MDM console is powerful, but unless you're the IT teacher it's hard to know where to click.
A login for every screen
"Put a policy on this class's iPads" means switching between the MDM console and Google Classroom.
Logs that don't say who
When everyone shares one admin account, nobody can tell who sent which command.
Device management in one sentence
Say what you want done. Claude checks the class roster, picks the iPads, and applies the policies and apps your school already set up in Argos MDM. ChatGPT can connect in beta, and Gemini is coming soon. GCsoft connectors are best optimized for Claude.
Check devices
See iPad status by grade, class, or lesson.
“Any grade 8 iPads not connected?”Deploy policies
Pick targets from the class roster and apply per-platform (iOS, Android, ChromeOS) policies.
“Put the exam policy on the exam classes”Deploy apps
Install apps registered in Argos MDM on class devices. Save frequent sets as quick groups.
“Install the lab app on science iPads”Sync · Push · Reboot
Wake devices that missed a policy, resync them, and reboot if needed.
“Resync class 3's iPads”With School Helper
Add School Helper (timetables and student search) and Claude turns "next period" or "period 3" into the actual class to pick targets.
“Get next period's devices ready”Risky actions are admin-only
Wipes and OS updates require admin rights, and targets are shown for confirmation first.
Nothing goes out unconfirmedA day without opening the console
Before period 1: iPads ready
Targets come from the class roster, and apps and policy go out together. With School Helper, the timetable works too.
“Install the math app on period 1 grade 7 class 2 iPads and apply the class policy”Mid-class troubleshooting
Find disconnected devices, wake them, and resync.
“Wake any grade 8 class 3 iPads that aren't connected”Exam prep
Apply the school's exam policy to only the classes sitting the exam.
“Put the exam policy on the period 5 grade 9 exam classes”Before leaving: check the log
Every deployment today, with who and when.
“Summarize who ran today's deployments”Common questions before adopting
Do we need to replace Argos MDM?
No. We connect the admin account you already use. No re-enrollment, no new policies.
What can teachers ask Claude to do?
Check devices, target by class, deploy policies and apps, sync, push, reboot. Wipes and OS updates are admin-only, with confirmation.
Is it logged who did what?
Each teacher signs in with their own account, and commands via Claude are logged with who ran them.
Anything to install at school?
No. We prepare and run the servers. Teachers add the GC EDU connector in Claude and sign in with their school Google account.