Messages, conversations, and role specific dashboards
Internal messaging, channel conversations, in-app notifications, and dashboards tailored to staff, teachers, parents, and students, so announcements land where people already work, not in yet another inbox. Schools send hundreds of small messages every week: fee reminders, exam updates, leave approvals, admissions nudges. Schoolyi keeps internal mail, team conversations, and notification preferences inside the same app people use for their daily tasks. Role-specific dashboards surface what matters to each audience without overwhelming them.
Outcomes
Practical results schools report after rolling out this area on the shared calendar and roster.
Staff communicate without leaving the operational system
Parents get fee, grade, and attendance updates in their portal
Templates speed up recurring messages for fees and admissions
Leadership dashboards keep principals informed day to day
Product truth
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Deep dive
Use these details to turn a product page into an implementation conversation.
Schools send hundreds of small messages every week: fee reminders, exam updates, leave approvals, admissions nudges. Schoolyi keeps internal mail, team conversations, and notification preferences inside the same app people use for their daily tasks. Role-specific dashboards surface what matters to each audience without overwhelming them.
Internal messaging, channel conversations, in-app notifications, and dashboards tailored to staff, teachers, parents, and students, so announcements land where people already work, not in yet another inbox. Because Communication & portals shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Everything included in this module, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
From the blog
Parent portals that cut front-office call volume
One login for every child: fees due, receipts, grades, attendance, and exams - without calling the office for each question.
Read the guide →Focused pages for evaluators comparing specific communication & portals workflows during an SMS rollout.
Workflow
A typical path from setup through daily use on Schoolyi.
inbox, sent, compose
Part of the Communication & portals workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Communication & portals workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Communication & portals workflow on Schoolyi, connected to roster, calendar, and role permissions.
Deep dive
Long-form context for evaluators comparing modules during an SMS rollout.
Schools send hundreds of small messages every week: fee reminders, exam updates, leave approvals, admissions nudges. Schoolyi keeps internal mail, team conversations, and notification preferences inside the same app people use for their daily tasks. Role-specific dashboards surface what matters to each audience without overwhelming them.
Internal messaging, channel conversations, in-app notifications, and dashboards tailored to staff, teachers, parents, and students, so announcements land where people already work, not in yet another inbox. Because Communication & portals shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
These areas work closely with communication & portals and share the same calendar, roster, and role model.
Straightforward answers for visitors evaluating the product.
All roles, Parents, Front office run daily workflows in this module while leadership reviews dashboards and exports when needed.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Dates, working days, and class structure flow from the shared calendar so downstream modules do not maintain parallel date lists.
Set the academic calendar before enabling dependent workflows, then test one holiday and one working-day exception against the resulting attendance or exam view. Keep the school’s local policy as the authority for edge cases.
Schools often launch admissions, roster, and fees first, then add this module when the foundation data is stable.
Choose the next phase only after the team has reconciled one complete operating cycle. Record the data, role, calendar, and support dependencies before widening access.
Role-scoped workspaces show only the tasks each team needs. Most schools run a short coordinator session plus self-serve docs.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
We'll show how this module fits your school's workflows and which teams benefit first.
Already using Schoolyi? Sign in
