In-app bell, email alerts, and deep links
Deliver fee, attendance, exam, and transport alerts through the in-app notification bell and email, with preferences and deep links into the right portal screen. Operational alerts only help when people see them. Schoolyi routes notifications to the bell, email, and parent portal deep links so families tap straight into the fee due, absence alert, or exam update that matters.
Outcomes
Practical results schools report after rolling out notifications inside communication & portals.
Families act on alerts without calling the office
Staff see approvals and tasks in one bell feed
Deep links reduce “where do I click?” support calls
Preferences respect who wants email vs in-app only
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.
Operational alerts only help when people see them. Schoolyi routes notifications to the bell, email, and parent portal deep links so families tap straight into the fee due, absence alert, or exam update that matters.
Deliver fee, attendance, exam, and transport alerts through the in-app notification bell and email, with preferences and deep links into the right portal screen. Because notifications lives inside communication & portals on Schoolyi, 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 capability, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
Full module
Communication & portals
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.
Explore Communication & portalsWorkflow
A typical path from setup through daily use on Schoolyi.
Part of the Notifications workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Notifications workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Notifications workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Notifications workflow on Schoolyi, connected to roster, calendar, and role permissions.
Deep dive
Long-form context for evaluators comparing capabilities during an SMS rollout.
Operational alerts only help when people see them. Schoolyi routes notifications to the bell, email, and parent portal deep links so families tap straight into the fee due, absence alert, or exam update that matters.
Deliver fee, attendance, exam, and transport alerts through the in-app notification bell and email, with preferences and deep links into the right portal screen. Because notifications lives inside communication & portals on Schoolyi, teams stop reconciling exports between spreadsheets and the parent portal.
These areas work closely with notifications inside communication & portals.
Straightforward answers for visitors evaluating the product.
Notification events can appear in the in-app bell and through email, with parent portal deep links taking families to the relevant screen.
Test the guardian link and publication boundary with a sample family before inviting the wider parent community. Confirm that each linked child exposes only the records the school intends.
Each user can manage notification preferences, including whether supported alerts should arrive in-app, by email, or through configured parent channels.
Test the guardian link and publication boundary with a sample family before inviting the wider parent community. Confirm that each linked child exposes only the records the school intends.
Supported alert types include fee, attendance, exam, and transport updates, with the recipient’s role and linked records determining visibility.
Before the first collection cycle, reconcile one paid, partially paid, and overdue student account so the family receipt and finance view agree. Keep any tax, gateway, refund, or accounting boundary as an explicit deployment decision.
Read and unread state remains visible in dashboards and the notification bell, so staff can distinguish a new task from an already reviewed alert.
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 notifications fits your school's communication & portals workflows and which teams benefit first.
Already using Schoolyi? Sign in
