Start with the task, not a wall of menus
An admissions officer needs application follow-up. A teacher needs classes, attendance, curriculum and homework. The bursar needs charges and collection review. Transport, library and facilities staff have their own registers and requests. Role-specific desks group these actions so that a person can start their day without searching across unrelated business modules.
Permissions must apply to the records
A navigation link alone is not security. Each read and change is checked against the signed-in school, role and record scope. Teachers work within assigned classes; students and guardians see their linked records. Staff cannot obtain a broader data set simply by opening a report or changing a URL. Leadership can review the operational picture across authorized desks.
Make the template your own
Use the demonstration to agree responsibilities before onboarding staff. Replace sample identities, verify guardian links and set the real academic year and class capacities. Review cloned process definitions before enabling them. Paid school operations, exports and chatbot access depend on the package selected; free business essentials do not automatically include the academic back office.