Compass Integration Overview
The Compass integration allows Junipa to synchronise student data directly from your school's Compass Student Information System. This eliminates the need to manually enter or update student records in Junipa.
What It Does
When the Compass integration is active:
- Student records are imported from Compass into Junipa, including names, year levels, and class assignments.
- Data stays in sync -- Changes made in Compass (e.g., new enrolments, year level changes, student departures) are reflected in Junipa automatically.
- Reduces manual work -- Staff do not need to manually add students or update their details in Junipa.
What Data Is Synced
| Data | Synced? | Notes |
|---|---|---|
| Student name | Yes | First name and last name |
| Year level | Yes | Updated when changed in Compass |
| Class/group assignments | Yes | Used for timetable views |
| Date of birth | Yes | If available in Compass |
| Enrolment status | Yes | Active, departed, etc. |
| Attendance data | Yes | If enabled |
| Disability categories | No | Must be set manually in Junipa |
| Adjustment levels | No | Must be set manually in Junipa |
| Evidence entries | No | Evidence is created only within Junipa |
How It Works
- Your school's Compass instance is configured to allow API access for Junipa.
- Junipa connects to Compass using secure API credentials.
- Student data is pulled from Compass on a scheduled basis (typically daily).
- New students are added to Junipa, and existing records are updated to match Compass.
If an import goes wrong
An import writes to records the whole school relies on, so Junipa keeps a way back.
Every import takes a backup first
Before an import writes anything, Junipa captures the current state of every record it is about to touch. The backup is taken as part of the import, not as a separate job you have to remember to run, and it covers the records in that import rather than the whole school. That keeps the restore precise: putting one bad import back does not roll the rest of the school back with it.
Rolling an import back
Administrators can roll an import back from the Timetables page. Find the import you want to undo and choose the rollback action. Junipa restores the records that import changed to the state captured in its backup.
Roll back when the import applied a file that turned out to be wrong, when a source system sent a partial extract, or when the review step was applied in error. Roll back promptly. The longer an incorrect timetable sits in Junipa, the more staff work is built on top of it.
Detached records and how to clear them
Sometimes an import leaves a record without its link to the source system. A class that no longer appears in the extract, or a student whose identifier changed at the source, becomes detached: the record is still in Junipa, but nothing in the source system points at it any more.
Detached records are listed in the remediation view under Integration. For each one you can:
- Restore the record, putting it back the way it was before the import that detached it.
- Relink the record to the correct record in the source system, which is the right choice when an identifier changed rather than the record disappearing.
- Dismiss the record, which is the right choice when the detachment is expected, for example a class that genuinely no longer runs.
Work the list down rather than leaving it. A detached record is not broken, but it stops receiving updates from the source system, so it quietly drifts out of date.
Prerequisites
Before setting up the Compass integration, you will need:
- An active Compass account for your school
- Administrative access to Compass (to configure API credentials)
- Administrative access to Junipa (to enter the integration settings)
Next Steps
- Follow the Setup Guide to configure the integration.
- If you run into issues, check the Troubleshooting page.