How to remove students from SIS synced classes Follow
This article helps Hāpara administrators remove students from SIS-synced classes, either automatically using SIS data or manually with a CSV file.
If your school uses SIS integration with Hāpara, you might see students in Hāpara classes who have withdrawn or changed classes. You can remove these students by either:
Automatically removing any students who are no longer included in your latest SIS data, or
Manually removing specific students using a CSV file (remove_students.csv).
Note
If a student is leaving the school completely, follow the guidance in “Recommendations for managing students leaving the school” rather than using the steps below.
In this article
How to automatically remove students not in uploaded data
If your school uses SIS integration with Hāpara, you may find that classes still contain students who have withdrawn from your school or district. In the Hāpara Admin Console, you can choose to automatically remove students who are no longer included in the most recent data load from your SIS.
This option can be:
Turned on as a one-off setting for manual Data Loads, or
Turned on as a persistent setting for automated “Sync from SIS” loads.
Important note – read before enabling
Do NOT enable this option if any of the following are true:
You are unsure of how your data sync works.
Your sync or upload does not include all active students every time.
You are doing a partial data load (for example, just one grade level or a subset of classes).
Once this option is enabled, any students not included in a data load will be removed from class rosters in Hāpara. As a result:
Teachers will lose visibility into these students’ work in Hāpara tools.
Students will lose access to Hāpara Workspace and Student Dashboard for those classes.
Steps to enable automatic removal for SIS syncs
Open the Hāpara Admin Console.
From the Home page, click “Class rostering.”
Scroll down to “SIS integration settings,” then click “Edit configuration.”
Under the “Synchronise student data” option, select “Remove students not listed in the uploaded data.”
Click “Save configuration.”
Note about manual Data Loads
For one-off manual Data Loads, the “Remove students not listed in the uploaded data” option can be selected on the load screen. Only use this option if your CSV includes all currently enrolled students who should remain in classes.
How to manually remove students from SIS synced classes
If you only need to remove specific students (for example, a small number who have withdrawn or changed classes), you can do this manually using a CSV file.
Follow these steps:
Create a CSV file and name it:
remove_students.csvIn the first row of the file, type the header:
email-
On each subsequent row, enter the Google username (email address) for one student who should be removed from classes.
Each row should contain only one student email.
Make sure the email addresses match the accounts used in Hāpara.
In the Hāpara Admin Console, go to:
Class rostering > Admin managed roster > Manual load.Click “Load student data.”
Select the remove_students.csv file you created.
Click “Start load.”
After the load completes, go to “Data logs” from the Class rostering section in the Hāpara Admin Console.
Open the Load Details for the remove_students load and review the log messages to confirm that students were removed from their classes successfully.
Notes
This process removes students from SIS-synced classes in Hāpara but does not remove their Google accounts.
If a student should no longer appear in classes going forward, make sure your SIS data also reflects the correct enrolments.
Additional tips
Test first with a small group of students to confirm the results before applying automatic removal widely.
Coordinate with your SIS or data team to ensure every sync or upload includes all active students so that you do not accidentally remove students who should remain enrolled.
Keep a copy of your remove_students.csv file and any related logs for auditing or troubleshooting.
If your school has frequent enrollment changes, consider scheduling regular manual loads or reviewing Data logs after each automated sync.