Administration portal
School setup, users, admissions, enrollment, records, academics, finance, operations, workflows, reports, and institutional oversight.
Skoolee access and architecture
Extend one governed school platform to every approved user, device, branch, and connected system.
Skoolee combines role-based web portals, mobile access, multi-school visibility, data migration, configurable reporting, deployment services, security, and controlled integration so the platform can operate as part of the school’s wider technology environment.
- Role-based self-service
- Mobile access
- Multi-school head office
- Controlled data exchange
Selected schools, universities, and organizations working with White Mountain Technologies.
Overview
Treat access, deployment, and integration as part of the product—not as afterthoughts
A school platform succeeds only when the right people can use it, the right data reaches it, and its outputs fit the institution’s wider operating environment. Portals, mobile access, identity, security, migration, reporting, hosting, and integration therefore need to be designed together with the functional modules.
Skoolee provides role-focused web experiences for administrators, teachers, students, parents, and guardians. Supported mobile scenarios make common teacher and family tasks easier to reach. Multi-school structures can provide head-office visibility while retaining approved school-level boundaries. A multilingual interface can help approved users work in the language experience configured for their environment.
WMT plans data migration, deployment, and integration against the school’s actual systems and constraints. The objective is controlled exchange and clear ownership—not a collection of ungoverned interfaces.
Role-based portals
Give each user group a purposeful experience rather than the entire system
The portal structure uses the same institutional data while limiting information and actions according to role, relationship, and responsibility.
Teacher portal
Schedules, rosters, planning, assignments, resources, attendance, conduct, grading, appraisals, communication, and class reporting.
Student portal
Schedules, assignments, resources, deadlines, activities, attendance, results, report cards, messages, and personal information.
Parent and guardian portal
Child-specific attendance, conduct, assignments, grades, reports, conferences, communications, services, and approved financial information.
Head-office access
Consolidated and comparative views across schools, with permissions and data boundaries aligned to the group’s governance model.
Specialized operational access
Purpose-specific access for admissions, finance, payroll, medical, transport, library, store, activities, support, and other approved roles.
Mobile access
Bring common teacher and family responsibilities closer to the moment they occur
Skoolee Mobile supports practical teacher and family scenarios such as schedules, attendance, assignments, resources, gradebook information, report cards, posts, notifications, and student progress. The exact mobile functions available depend on the supported application release and the school’s configured modules.
Mobile access should complement—not fragment—the web platform. The same user identity, permissions, student relationships, and source records should determine what is available. A change entered through an approved mobile workflow remains part of the institutional record rather than a separate copy.
The launch plan should address device support, account activation, password recovery, notifications, privacy, support responsibilities, and the communication needed to help teachers and families use the application correctly.
Teacher scenarios
View schedules and rosters, take attendance, work with assignments, review student information, and access approved grading or reporting functions.
Parent and guardian scenarios
Follow posts, responsibilities, attendance, assignments, results, report cards, and approved school communication.
Notification design
Define which events justify a mobile notification, how frequently users are alerted, and where the authoritative detail is displayed.
Support and adoption
Prepare activation instructions, user guidance, support channels, privacy expectations, and a process for account or relationship corrections.
Integration and data exchange
Connect Skoolee to the wider school technology environment through governed interfaces
The integration method is selected according to the connected system, data ownership, timing, security, technical capabilities, and operational responsibility.
Data migration
Extract, clean, map, transform, load, reconcile, and approve existing student, family, staff, academic, financial, service, and historical data.
File exchange
Use controlled CSV or other agreed file formats where scheduled or manual exchange is the appropriate integration method.
APIs and services
Use approved APIs or service endpoints where supported by the connected systems and the required security model.
Database tables or views
Exchange data through agreed staging tables or database views when the institution’s architecture and governance support that approach.
Identity and access
Plan account provisioning, email identity, single sign-on readiness, authentication, role assignment, and deactivation responsibilities.
Reporting and exports
Provide approved data extracts, reports, dashboards, and downstream feeds without creating uncontrolled duplicate sources.
Monitoring and exception handling
Log exchanges, validate counts and keys, identify rejected records, retry approved failures, and assign responsibility for resolution.
Data ownership
Document which system is authoritative for each entity and field, including the direction and timing of every exchange.
Deployment and rollout
Move from source systems to a supported operating environment in controlled stages
Deployment includes the platform, configuration, migration, security, testing, training, and operational support required for a stable launch.
- 01
Assess
Review infrastructure, users, devices, connectivity, identity, source systems, data volumes, integrations, security, and service expectations.
- 02
Provision and configure
Prepare the environment, domains, HTTPS, database, backups, access, school structures, modules, roles, reports, and notifications.
- 03
Migrate and integrate
Load validated data, establish approved interfaces, reconcile records and totals, and test complete operational scenarios.
- 04
Train and pilot
Prepare administrators and user groups, test in representative schools or departments, record issues, and confirm launch readiness.
- 05
Launch and support
Execute cutover, monitor usage and integrations, manage issues, support adoption, and plan the next approved phase.
Security, reliability, and governance
Protect access and continuity through explicit responsibilities
Skoolee access is controlled by user identity, role, relationship, and approved privileges. The implementation should define account creation, activation, password or single-sign-on behavior, role assignment, periodic review, and timely deactivation.
Production deployment should enforce HTTPS, backups, environment separation, secure configuration, monitoring, error handling, and a documented recovery approach. The exact hosting and operational responsibilities are confirmed for each client implementation.
Because schools manage personal, academic, financial, and medical information, permissions and data exchange should follow least-privilege principles. Sensitive exports, support access, test data, and integration credentials need the same governance as the application itself.
Role-based access
Map roles to screens, data, actions, approvals, reports, exports, and school or branch boundaries.
Environment control
Separate production from testing, protect configuration and credentials, and prevent unfinished environments from being publicly indexed.
Backup and recovery
Define backup frequency, storage, restore testing, responsibilities, recovery priorities, and communication procedures.
Operational support
Document monitoring, incident reporting, escalation, integration ownership, maintenance, and user-support channels.
Questions
Frequently asked questions
Which user portals are available?
Skoolee provides role-based experiences for administrators, teachers, students, parents, and guardians, with specialized access for approved operational and head-office roles.
Does Skoolee have a mobile application?
Yes. Supported mobile scenarios are available for teacher and family use, complementing the wider responsive web platform.
Can Skoolee support a group of schools?
Yes. Multi-school and head-office structures can provide consolidated visibility while respecting school-level structures, roles, processes, and data boundaries.
How can Skoolee exchange data with other systems?
Depending on the connected system and architecture, exchange can use approved files, APIs, services, database tables, views, or other controlled methods.
Can existing data be migrated into Skoolee?
Yes. Migration includes source assessment, mapping, cleaning, transformation, loading, reconciliation, exception resolution, and approval.
Can Skoolee be hosted in the cloud?
Yes. Cloud deployment and managed services can be included in the implementation scope, with security, backups, monitoring, support, and responsibilities defined for the client environment.
Next step
Plan the Skoolee architecture around your school environment
A technical and functional session can review portals, mobile use, identity, multi-school structure, hosting, security, data migration, integrations, reports, support, and phased rollout.