School Onboarding Checklist
Use this checklist when a school is moving from "Junipa is provisioned" to "staff can safely start work". It is written for a generic school instance, not a live customer tenant.
Your school URL should look like yourschool.junipa.com.au. Replace yourschool with the approved Junipa subdomain for the school.
Confirm the school instance
Before staff are invited, confirm:
- The school name is correct.
- The Junipa subdomain is correct.
- The primary administrator is correct.
- The school year, term dates and time zone are correct.
- The school knows whether staff will use Microsoft, Google or Junipa sign-in.
- The first workflow is agreed: evidence, plans, reporting or dashboard use.
Do not use another school's URL, name, student data or staff list as the example for a new school.
Confirm sign-in
Choose the sign-in path before staff are invited.
| Sign-in path | Use when | Check before launch |
|---|---|---|
| Microsoft Entra ID | Staff use Microsoft 365 accounts | The school domain and redirect settings are approved by IT. |
| Google sign-in | Staff use Google Workspace accounts | The school domain is approved and staff emails match school records. |
| Junipa auth | The school needs direct Junipa accounts | Administrators know who can create and reset accounts. |
For setup details, see Single Sign-On and the SSO setup guide.
Confirm student data
Students can be added through an integration or an agreed import path.
Before launch, confirm:
- The student management system or import file is the school source of truth.
- Current students are included.
- Departed students are not treated as current students.
- Year levels are correct.
- Student identifiers are consistent between the school source and Junipa.
- Disability categories and adjustment levels are only imported when they are approved for use.
- The school knows who will check missing or duplicated records.
If the school uses Compass or Wonde, start from Integrations. If the school needs a manual import first, agree who owns the file and how corrections will be handled.
Confirm staff and roles
Staff should only receive the access they need.
| Role | Typical access |
|---|---|
| Administrator | School settings, users, students, reports and configuration. |
| Teacher | Assigned students, evidence entry and relevant plans. |
| Case manager | Student records, evidence, plans and follow-up work for assigned students. |
| Leadership | Reporting and school-wide review views. |
Before inviting staff, check:
- Names and email addresses are correct.
- Each person has the right role.
- Staff who should not see student-level information are not added to student-level roles.
- Departed staff are not invited.
- At least two administrators are available for continuity.
See Team management for the staff workflow.
Configure the school structure
Set up the basic structure before teachers start recording evidence.
- Open Administration > School Settings.
- Confirm the academic year and term dates.
- Confirm year levels.
- Confirm student groups or cohorts the school will use.
- Check whether timetable data is needed for the dashboard.
- Save the settings and review them with the school administrator.
If timetable data is used, test it with a small staff group first. Teachers should be able to find the right students without searching through the whole school.
Prepare the first workflow
Do not try to launch every Junipa workflow on the first day. Pick one clear starting point.
Good first workflows:
- Add evidence for a known student group.
- Review the dashboard for a teacher cohort.
- Create or update a student plan.
- Check the Audit Report for thin records.
- Use Student Activity to find students needing a decision.
- Review the School Hubs reporting view before submission.
The goal is a calm first use: one group, one task, one clear next action.
Go-live check
Before wider staff rollout:
- The school URL is correct.
- Administrator access has been tested.
- Sign-in has been tested with a real staff account.
- A sample student record has been checked.
- Student identifiers match the school source.
- Staff roles have been reviewed.
- A teacher can find assigned students.
- A teacher or case manager can add evidence.
- A file attachment can be added where required.
- Reports open with expected data.
- The school knows who to contact for support.
After launch
Review the first week with the school administrator.
- Which staff logged in?
- Which students were updated?
- Which evidence records were added?
- Were any students missing or duplicated?
- Did teachers know what to do next?
- Is the first workflow ready to expand?
When the first workflow is working, move to the next one. That might be plans, reporting, signatures, curriculum adjustments or organisation oversight.