The Infocare Student Leave Module connects family requests, school approval policies, and attendance records in one workflow. Schools configure approval thresholds, staff assignments, and attendance settings to match their own policies.
At a glance
The leave module at a glance
- ✓Two parent entry points — Submit through PowerSchool Parent Portal or OnePortal, the WeChat Mini Program.
- ✓Automatic approver assignment — Route each request using the student’s class, grade, and the school’s staff assignments.
- ✓Up to three approval levels — Short leave goes to the homeroom teacher; longer leave adds the grade head and, when required, a senior leader.
- ✓Teacher and Admin Portal review — Staff review requests within their assigned responsibilities and record a decision.
- ✓Attendance after final approval — The integration automatically updates PowerSchool Attendance using the school’s configured codes.
- ✓Visible progress and history — Families follow request progress; authorized staff can trace approvals and attendance update results.
01
A leave request can pass through several people before attendance catches up
A parent sends a message, the homeroom teacher checks the dates, and a longer absence needs a grade head or senior leader’s decision. Someone then has to enter the approved absence into PowerSchool. When those steps happen in separate conversations, it is easy to lose track of the current decision.
- Unclear ownership
Staff must work out who should approve a request and forward it to the correct person.
- Scattered decisions
Families and school teams search messages to confirm whether every required approval is complete.
- Attendance delays
An approved request still requires another person to copy the dates and absence code into the attendance record.
02
One leave record, from the parent’s request to the school’s final decision
The module gives families two familiar ways to begin: PowerSchool Parent Portal on the web, or OnePortal in WeChat. Both channels use the same leave service, approval rules, and request history, so staff can review requests in one workflow regardless of where they were submitted.
The student’s class determines the homeroom approver. Leave duration determines whether the request also needs a grade head and a senior leader. Each required stage follows the previous approval, and only the final approval makes the request ready for an attendance update.
A Class 1 request appears in the Class 1 homeroom teacher’s queue. The Class 2 teacher cannot see it unless separately authorized. Grade heads and senior leaders receive access according to their assigned grade or school responsibilities.
03
A familiar place for every step
Parents submit the dates and reason; teachers and authorized administrators review the request in their own portals. The PowerSchool previews below illustrate the submission, review, and configuration steps. The OnePortal screenshot shows recent leave requests and their approval status in the WeChat Mini Program. The previews and screenshot use different example records; they do not show one continuous request.
Parents: request leave on the web or in WeChat
After selecting a linked child, a parent enters the leave period, leave type, and reason. Before submission, the form shows the student and requested dates for checking. The status view makes it clear whether the request is awaiting review, approved, or rejected.
Staff: review the requests assigned to you
The Teacher Portal queue focuses on the homeroom teacher’s assigned students. Grade heads, senior leaders, and authorized administrators can review their assigned stages through the Teacher or Admin Portal, according to their role. Request details include the leave period, reason, and decisions already recorded.

Administrators: configure the school’s approval policy
The configuration separates duration rules from staff assignments. A school can define a two- or three-level policy, set the duration that adds each level, and map each class to its homeroom teacher. Grade and school assignments determine the higher-level approvers.
04
Complete the approvals, then update attendance
The approval chain starts with the homeroom teacher. A request above the school’s first duration threshold continues to the grade head; one above the next threshold continues to a designated senior leader. In a two-level policy, the grade head is the final approver for longer leave.
- Submit
A parent requests leave through PowerSchool Parent Portal or OnePortal.
- Assign
The student’s class and leave duration determine the required approvers.
- Approve
Each required approver records a decision in sequence.
- Update
Final approval triggers the configured PowerSchool Attendance update.
A rejection ends the current approval chain without updating attendance. Requests still awaiting any required approval also leave attendance unchanged. After final approval, the integration applies the school’s mapped attendance code to the approved leave period, using the school calendar and attendance configuration.
An approved request may still be waiting for PowerSchool to accept the attendance update. The staff view distinguishes “Approved,” “Attendance updated,” and “Attendance update needs attention,” so a failed update remains visible and can be retried.
05
A shared service behind the parent and staff experiences
The architecture keeps requests, approval decisions, and integration results together. PowerSchool supplies the student and school context; the leave service coordinates the workflow across the portals and OnePortal.
- Connected parent channels: PowerSchool Parent Portal and OnePortal call the same leave service. Each channel verifies the parent’s identity and relationship to the selected student.
- Scoped staff access: Teacher and Admin Portal access is checked against class, grade, school, and role assignments on every request, including when a staff member opens a direct link.
- Configurable approval rules: the service resolves the required stages and approvers from the school’s duration policy and staff mappings. Missing approver assignments are flagged for resolution before a request can progress.
- Recorded decisions: each stage retains the approver, decision, comment, and time, giving authorized staff a traceable history.
- Attendance integration: automatic updates use the school’s authorized PowerSchool connection, attendance mode, calendar, and leave-type-to-code mappings.
- Recoverable updates: the service tracks each attendance write, prevents duplicate updates on retries, and flags conflicts with existing records for staff review. Authorized staff review attendance corrections when approved leave changes or is cancelled.
06
Less forwarding, clearer decisions, fewer manual entries
- For families
Submit from PowerSchool or WeChat and follow the request’s progress without contacting several staff members.
- For homeroom teachers
Review an assigned class queue, with the next approval stage determined by school policy.
- For school leaders
Review longer absences with the earlier decisions visible and a clear record of who approved each stage.
- For attendance teams
Reduce re-entry of approved leave and focus on update failures, conflicting records, and requests needing correction.
07
Common questions
PowerSchool Student Leave Module FAQ
Can parents use OnePortal instead of PowerSchool Parent Portal?
Yes. The module supports both PowerSchool Parent Portal and OnePortal, the WeChat Mini Program. Both connect to the same request and approval service, with access limited to the parent’s linked children.
How many approval levels does a request need?
It depends on the school’s policy and the length of leave. Short leave needs homeroom approval; longer leave adds a grade head, and the longest leave can add a senior leader. The module supports a two- or three-level policy with configurable thresholds.
Can a Class 1 teacher see Class 2 requests?
Not through their Class 1 homeroom assignment. Access rules scope the teacher’s queue to assigned classes. A separate grade-level or administrative role may grant broader access when the school authorizes it.
Where do teachers and administrators approve requests?
In the PowerSchool Teacher Portal or Admin Portal, depending on their role and access. The same approval history follows the request between stages.
When is PowerSchool Attendance updated?
After every required approval is complete, the module automatically updates PowerSchool Attendance using the school’s configured attendance codes and calendar. Pending or rejected requests do not trigger a leave attendance update.
What happens if an attendance update fails?
The approval remains recorded, while the attendance status shows that staff attention or a retry is needed. A successful update is shown only after the integration confirms the write result.
Can each school set its own approval thresholds?
Yes. Schools configure duration thresholds and the approval levels required for each band. The one-day and three-day values in the illustrative preview are examples; each school applies its own leave policy and duration rules.
Want a leave workflow that fits your school’s approval policy?
Infocare helps schools connect parent services, staff decisions, and PowerSchool operations. Start with your approval levels, class assignments, and attendance rules to shape a workflow for your school.
Talk to Infocare


