Guardian verification
Student-specific details are shared only after the sender’s number matches a registered guardian, and only for students they are authorized to see.
Schogle Connect is shared software, but every school operates in its own workspace. Authorization is enforced on the server for every request, not by hiding things in the interface.
| Role | Inbox | Payments | Fee data |
|---|---|---|---|
| Admin | |||
| Accountant | |||
| Class teacher |
Every school is its own tenant with its own WhatsApp configuration, contacts, conversations, AI knowledge and team.
When an administrator arrives from Schogle ERP, Connect links the new workspace to the right ERP School ID securely, so schools do not have to type it in by hand.
Student-specific details are shared only after the sender’s number matches a registered guardian, and only for students they are authorized to see.
The assistant can only call controlled tools. It never receives database access and cannot search another school’s content.
WhatsApp and AI provider credentials are held server-side and are never exposed to the browser.
Incoming WhatsApp events are signature-checked and resolved to the correct school before they are processed.
Duplicate prevention by UTR, verification before ERP entry, and accountant approval when a payment is uncertain.
Message, payment and administrative activity is logged for each school so teams can see what happened and when.
Staff see the conversations and tools their role allows. Administrators manage assignments and responsibilities.
Connect talks to Schogle ERP through authenticated, permission-controlled APIs. It never connects to the ERP database directly.
Connect runs separately from Schogle ERP, so messaging and AI workloads do not slow down school administration.