Isolated school tenants
Each school keeps its own sessions, classes, students, staff, finance settings, templates, and branding within its data boundary.
Designed around boundaries, not bolted on later
The right access for every campus, role, class, and section.
CampusPilot combines isolated school tenants, role-based permissions, and teacher assignment scopes so each protected operation retains the right operational context.
01
Permission boundaries
Connected does not mean exposed.
Explore how access becomes more specific from the authenticated platform request to the exact class and section assignment.
Access narrows
Access narrows
Access narrows
02
Security across the operation
Clear boundaries for people, campuses, finance, and connected tools.
Role-based permissions
Administrators, managers, accountants, exam coordinators, and teachers receive access around their responsibilities.
Assignment-based teacher scopes
Protected academic work can be limited to the classes and sections assigned to each teacher.
Separate student access
Student sessions are recognized independently and portal requests are restricted to the authenticated student’s own information.
Controlled connections
Session authentication serves the application while API keys support authorized connected tools and services.
Permission-aware MCP
The application API and native MCP connection apply the same authorization boundaries to protected operations.
Multi-campus operations
One account. The appropriate campus context.
Users associated with more than one school can choose the campus they need, while local records, settings, and permissions remain separate.
Your school is preparing students for the future.
Its operating system should be ready for it too.
Book a CampusPilot demo