Skip to content

Apps & Integrations

An app for every role, on one school record.

Parents, students, teachers, the office and leadership each get the screens their work needs. Everything they do lands on the same record, and the tools you keep can be connected as scoped work.

One institutional record

Synthetic data
One institutional record acted on from every surface: a guardian acknowledging a fee reminder, a teacher marking a register, finance applying an approved concession, transport notifying a route change, and the trust view already current without an export.

By audience

What each person does, and where

The standard parent and staff mobile apps are included in the licence; staff and leadership also work on the web.

Parents, teachers, principals, finance teams and trustees connected to one institutional record, each seeing the part their role owns.
Mobile app

Parents

  • Attendance and absence alerts
  • Fee dues, payments and receipts
  • Circulars and acknowledgements
  • Progress and results
Mobile app

Students

  • Timetable and the day's classes
  • Assignments due
  • Notices
  • Results
Mobile app and web

Teachers and staff

  • Class and period attendance
  • Marks entry and remarks
  • Messages to parents
  • Their own queue of follow-ups
Web

Administrators and office

  • Admissions and student records
  • Fee plans, concessions and reconciliation
  • Campus setup, roles and approvals
  • Circulars and communication logs
Web

Principals, trustees and leadership

  • Current position across campuses
  • Open exceptions and who owns them
  • Approvals waiting on them
  • Questions to AEGIS, inside their permissions

App-store availability, supported device versions and the modules in each app for your institution are confirmed in writing in your proposal. White-labelled apps under your own branding are a separately scoped option.

Integrations

What connects, and on what terms

SquareCampus does not publish a catalogue of pre-built connectors. Connecting another system is scoped work: we assess each tool during discovery, and what connects, in which direction, how often and at what cost is confirmed in writing before any build.

Sign-inBy plan
SquareCampus-managed credentials in every plan; Microsoft Entra ID single sign-on from Pro, subject to technical onboarding.
Payment gateway, SMS and WhatsAppScoped service
Payments run through your institution's own gateway account, and SquareCampus never handles the money. SMS and WhatsApp come with a monthly allowance; usage beyond it is prepaid.
Accounting software, biometric devices, LMS and government portalsScoped service
Assessed tool by tool. There is no pre-built connector; each one is scoped, quoted and confirmed in writing.
Development APIs for the institution's own appsScoped service
Scoped per institution and granted after a compliance review, inside the same role-based permissions and audit trail.

Prerequisites, pipelines into one dashboard and deployment options are set out on data and integration services.

Next step

See the apps for the roles in your institution.

Tell us which roles and tools matter most. We will show the relevant screens and map which of your current tools could connect.