School-year transitions
Clean handoff.New school year.
A clean handoff keeps people working on day one and closes access they no longer need. Start from approved changes and check each one.
Español1Why it matters
Handle joining changing and leaving
Connect access decisions to approved personnel and student lifecycle processes. Grant the access needed for the role, review changes when duties move and revoke unnecessary access when the relationship ends. Use accountable approvals for privileged changes. Stale-account tools provide review candidates; unfamiliar or missing activity must not trigger unreviewed mass disabling.
Plan the school-year handoff
At term end, follow the approved return and reset process rather than manually deleting random files. Identify devices used by departing staff or students and the role responsible for account changes. Save instructional work in approved storage before a planned reset. Try one classroom continuity exercise: what would the class do if the primary device or display were unavailable?
2Do this
- Start from the roster change
Begin from an approved roster change, not inactivity alone. Confirm who joins, moves or leaves, and when.
- Review access
Match account, group and app access to the new role. Authorize scoped changes; resolve substitute exceptions.
- Hand off devices
Track device return, issue and approved reset. Save instructional work in approved storage first.
- Confirm help and recovery
Check recovery owners and reporting contacts, including a known route when email is down.
- Close the loop
Confirm changes happened. Give each open item an owner. Record date, scope and result in the district system.
Close the loop- Owner named
- Change checked
- Result recorded
Spotted leftover access? Report it to the help desk. Catching it is part of a good handoff. Don't remove access or files on your own.
3Quick check
Want credit for this?
Sign in to Cyber Academy to take the full course, record your progress and earn a completion certificate.
Full course: Protect access across the account lifecycle · 18 min
We count visits to this page in aggregate only. No cookies, no accounts, no personal data.