SCHOOL MANAGEMENT · INFORMATION SECURITY
What Should Happen to ERP Access When a School Employee Leaves?
A structured offboarding checklist for removing access, transferring open work, protecting school records and preserving appropriate history.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
When an employee leaves, an authorised school owner should receive timely notice, review the person’s accounts and permissions, disable or adjust access through the supported process, transfer open work and preserve records the school needs. Verify how sessions, exports and activity history behave. Do not keep a former employee’s shared login active to avoid a hand-off.
01 / NOTIFICATION
Connect the departure decision to the system owner promptly.
Define which authorised HR or school leader notifies the account administrator and when. Include transfers, extended leave and role changes where permissions should be reconsidered, not only final departures.
Share only necessary employment information. The system owner needs the account identity, effective date and required action—not unrelated personnel details.
02 / ACCOUNT & ACCESS
Identify every account and permission associated with the employee.
Check the active account list, product roles, report access and approved shared storage. Determine what should be disabled or reassigned based on the person’s actual responsibilities and departure timing.
Confirm the product’s disable and session behavior. Do not assume removing a role terminates existing sessions or revokes exported files unless the provider verifies it.
03 / OPEN WORK
Transfer tasks and record ownership to authorised colleagues.
List unresolved admissions, fee questions, attendance corrections, report requests or academic tasks that need continuity. Assign each to a current role with suitable access and enough context to proceed.
Do not pass the departing employee’s password to a colleague. If work is associated with an individual profile, ask how attribution and ownership should be handled while preserving appropriate history.
04 / DATA COPIES & DEVICES
Address downloaded school information as well as in-product access.
Follow school policy for returning devices, removing approved credentials and handling local copies of reports. Check shared folders and temporary files where the person had access, while respecting privacy and lawful process.
A provider’s account change may not erase data previously exported to a device or email. Document the institution’s actions and any limitation that needs additional follow-up.
05 / HISTORY & RETENTION
Preserve operational accountability without retaining unnecessary access.
The school may need relevant activity history for continuity or review. Confirm whether it remains attributable after an account is disabled and who can retrieve it. Avoid deleting records if doing so would remove institutional context the school must preserve.
Apply the institution’s retention schedule and obtain qualified guidance for employment or legal questions. Account removal and record retention are separate decisions.
06 / VERIFY COMPLETION
Check that the access change worked and close the offboarding record.
Verify account status through an authorised check and confirm the receiving staff can perform assigned work. Record unresolved sessions, external copies or provider questions with an owner and due date.
Update the active-user register and review the process periodically. A clear departure routine protects school information while helping operations continue without shared credentials.
A FIELD GUIDE FOR YOUR TEAM
A school ERP departure checklist
Coordinate this with the school’s authorised HR and technology processes; share only the information each role needs.
| Lens | Question to ask | What to record |
|---|---|---|
| NOTIFICATION | Connect the departure decision to the system owner promptly. | A timely notification path with effective date and named reviewer. |
| ACCOUNT & ACCESS | Identify every account and permission associated with the employee. | An access inventory and verified removal procedure. |
| OPEN WORK | Transfer tasks and record ownership to authorised colleagues. | A task hand-off with new owners and due dates. |
| DATA COPIES & DEVICES | Address downloaded school information as well as in-product access. | A controlled device and exported-copy review. |
| HISTORY & RETENTION | Preserve operational accountability without retaining unnecessary access. | A documented access change and a retention decision. |
| VERIFY COMPLETION | Check that the access change worked and close the offboarding record. | A completion check, updated account register and closed hand-off. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
Confirm School ERP account deactivation, session revocation, record ownership and activity-history behavior with the provider. This guide does not claim automated HR-triggered offboarding or any particular deletion policy.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.