Universities and colleges create tens of thousands of student identities a year, and most of the access problems come not from enrolment but from the transitions afterwards: suspension, interruption, graduation, alumni status and the accounts nobody ever deletes. A student identity can pass through a dozen states between first application and final deletion, each with different entitlements, data obligations and risks. This guide defines those states, the events that move a person between them, what access each state should carry, and how to run the transitions with automation rather than annual clean-up projects. It goes deeper than the Education Identity Security Guide, which covers the threats and controls across education, and is written for identity architects, IAM engineers and IT service owners in higher and further education.
Key takeaways
- Model states, not just joiners and leavers. A student moves through applicant, offer holder, enrolled, interrupted, suspended, completed, graduate and alumnus states; each needs its own entitlement set.
- The student record system is the authority. Status changes should flow from the student information system into the identity platform, never from a help desk ticket or a manual spreadsheet.
- Alumni are not members. The eduPerson schema keeps "alum" separate from "member", so federated services should stop treating graduates as current community members.
- Grace periods need end dates. Every "keep it a bit longer" decision, such as email after graduation, must have an expiry date that the system enforces.
- Deletion is a lifecycle state too. Retention schedules under data protection law decide when an identity and its data are finally removed, and that step must be automated and evidenced.
Why the student lifecycle is different
The generic Joiner-Mover-Leaver Guide assumes an employee with a start date, an end date and an HR record. Students break those assumptions in five ways.
- Volume and seasonality: most joiners and leavers arrive in a few weeks around enrolment and graduation, so manual processes collapse under peak load.
- Ambiguous end dates: a course end date is not a leaving date. Students resit, appeal, take interruptions, submit theses late or wait months for an award to be conferred.
- Overlapping roles: one person can be a student, a part-time employee, a teaching assistant, a researcher and later an alumnus and staff member. Each role comes from a different system of record.
- A long tail after leaving: institutions often want a continuing relationship with graduates (careers services, alumni email, donations), which pulls against least privilege.
- Personal devices and personal data: students keep coursework, photos and personal files in institutional cloud storage and expect to take them with them.
Lifecycle states and the access each one carries
Define states centrally, publish them, and map every service to them. The table is a starting model; adapt names to your student record system, but keep every state explicit.
| State | Entered when | Typical access | Exit trigger |
|---|---|---|---|
| Applicant | Application submitted | Admissions portal only, with a low-assurance account not linked to the directory | Offer made, application withdrawn or rejected |
| Offer holder | Offer issued | Pre-arrival portal, accommodation, limited online induction | Enrolment, or offer declined or lapsed |
| Enrolled | Registration completed and identity checked | Full student entitlements: email, learning platform, library, Wi-Fi, software, federated research services | Interruption, suspension, withdrawal, completion |
| Interrupted | Approved break in study | Email and personal storage, no teaching systems or licensed software | Return to study or withdrawal |
| Suspended | Disciplinary, financial or safeguarding hold | Defined by policy; often email only, sometimes nothing | Hold lifted or withdrawal |
| Withdrawn | Student leaves before completing | Short grace period for data export, then disabled | Grace period ends, or re-enrolment |
| Completed, awaiting award | Final assessment submitted | Email, storage, results and appeals portals | Award conferred or appeal concluded |
| Graduate (grace period) | Award conferred | Email and storage for a fixed export window; no licensed software or library resources | Window ends |
| Alumnus | Opted in to alumni services | Alumni portal, optionally alumni email in a separate scope; no student services | Opt-out or inactivity threshold |
| Disabled | Access ended, records still held | No sign-in; data held for retention | Retention period ends |
| Deleted | Retention period ends | None; identifier reserved against reuse | Final |
Two design rules prevent most problems. First, identifiers (usernames, email addresses, persistent federation identifiers) are never reassigned to another person, even after deletion, because a recycled address can receive mail, password resets and federated access intended for the previous holder. Second, a person with several roles gets the union of the entitlements their active roles grant, and losing one role removes only that role's entitlements. See the Birthright Access Design Guide for how to keep default entitlements small.
Sources of truth and lifecycle events
The identity platform should never decide a student's status on its own. It consumes events from authoritative systems and applies rules.
| Event | Authoritative source | Identity action | Timing |
|---|---|---|---|
| Application submitted | Admissions system | Create applicant account outside the main directory | Immediate |
| Enrolment completed | Student information system | Create or promote directory identity; assign student role | Immediate, after identity check |
| Interruption approved | Student information system | Remove teaching and licensed entitlements; keep email | On the approved start date |
| Suspension or hold | Student information system, case management | Apply the policy-defined access set | Immediate |
| Withdrawal | Student information system | Start withdrawal grace period | On the effective date |
| Award conferred | Student information system (awards) | Move to graduate grace period; remove student role | On conferral |
| Alumni opt-in | Alumni relations system | Assign alumni role in its own scope | On opt-in |
| Employment starts or ends | HR system | Add or remove staff role independently of student role | On contract dates |
| Retention period reached | Records management schedule | Delete identity and data; record evidence | Scheduled job |
The common gap is that the student record system tracks academic status well but nobody maps those codes to identity states. Hold a joint workshop with registry, admissions, alumni relations and IT to agree every status code and the state it maps to. Codes that map to nothing are where orphaned accounts come from. The Identity Lifecycle Event Design Guide covers event design patterns in depth.
Identity proofing and the applicant to student handover
Applicant accounts are created by the public at low assurance, often with a personal email address. The risk is promoting that account straight into a full student identity without checking that the person enrolling is the person who applied. NIST SP 800-63A-4, published as final in July 2025, sets requirements for identity proofing and enrolment at three identity assurance levels and is a useful reference for choosing the level of checking at enrolment.
- Keep applicant and student identities separate: issue the institutional identity at enrolment and link it to the applicant record, rather than upgrading the applicant's self-registered login.
- Check identity at enrolment: in person or remotely against the evidence the institution already requires for registration, and record the method.
- Bootstrap credentials safely: deliver first-time activation through a channel bound to the checked identity, then require MFA registration before full access. See the Account Recovery and Help Desk Security Guide for help desk verification, which matters most in the first weeks of term.
See the Identity Proofing and KYC Guide for proofing methods.
Federation attributes: student, alum and member
Most institutions release affiliation attributes to research and library services through academic federations. The REFEDS eduPerson specification (version 202111) lists the permissible values of eduPersonAffiliation as faculty, student, staff, alum, member, affiliate, employee and library-walk-in. Two rules matter for the lifecycle.
- member must be asserted for anyone with a faculty, staff, student or employee affiliation, and is not asserted for alumni, because alumni do not hold the full set of basic institutional privileges.
- alum is a separate value, not a flavour of student. When a student graduates, the identity provider should stop releasing student and member and, if the person is an alumnus, release alum.
eduPersonScopedAffiliation adds the institution's domain (for example [email protected]), and eduPersonEntitlement carries URIs for specific rights such as a licensing agreement. Library and publisher services often grant access on member or student; if the release policy is not driven by the lifecycle state, graduates keep licensed access the institution is not entitled to give them. See Shibboleth and Academic Federations for identity provider configuration.
Graduation, alumni accounts and platform settings
Graduation is the transition that fails most often, because institutions try to be generous and end up with indefinite access. Decide three things in policy: how long graduates keep email and storage, whether alumni get a continuing account at all, and where that account lives. The two most common student productivity platforms both document settings for this. Platforms are listed alphabetically; order is not a ranking.
Google Workspace for Education
- Content transfer: administrators enable "Allow users in this organizational unit to access Transfer your content" under Data, Data import and export, Google Takeout, and choose which services (Drive, Gmail, Photos) can be transferred. Google states the permission is on by default for all organisational units and that transfer creates copies without deleting originals. Gmail transfer covers email only, not contacts, chats or tasks.
- Prerequisites: Google Takeout must be on for the users, and external Drive sharing must be on for users to transfer Drive files they own.
- Suspension: suspending a user blocks access to Workspace services while keeping email, documents and other data, and the account can be restored. Collaborators keep access to documents already shared with them. Suspended accounts are billed at the same rate as active accounts, so suspension suits a short hold before deletion rather than a permanent state.
- Organisational units: place graduates in a dedicated organisational unit so that transfer settings and policies apply to that group only. See the Google Workspace Security Guide.
Microsoft 365 Education
- Alumni licence: Microsoft documents a free Exchange Online for Alumni licence that lets graduates keep school email, and describes two approaches for higher education: change the existing account's licence to the alumni licence, or block or remove the student account and create a new one in a tenant designated for alumni, which separates alumni from current students.
- Licence reclamation: when a student licence is reclaimed, mailbox data is held for 30 days (longer under legal hold) and then deleted; the OneDrive is not deleted with the licence and continues to count against storage until it is cleaned up.
- Block or delete: Microsoft advises deleting accounts where no retention requirement applies and blocking sign-in where records must be kept. For accounts synced from on-premises Active Directory, disable or remove them there too, or Microsoft Entra Connect recreates them on the next sync.
- Timing and retention: Microsoft's academic year transition guidance suggests identifying accounts three weeks before the end of the school year and acting after it ends, and points to event-driven retention that can start a retention period on an event such as graduation. See Entra ID Governance Lifecycle Workflows.
Choosing an alumni model
| Model | How it works | Best when | Trade-off |
|---|---|---|---|
| Hard stop | Export window, then disable and delete | Smaller institutions, or where alumni services use their own logins | Graduates lose the institutional address |
| Same account, reduced role | Student role removed, alumni role added in the same directory | Strong role-based automation already exists | Alumni remain in the main directory and in scope for phishing, password spraying and access mistakes |
| Separate alumni scope | New identity in a separate tenant, domain or directory | Large alumni programmes wanting lifelong email | Second environment to run; mail forwarding and identity linking to manage |
| External identity | Alumni sign in with a personal or social account linked to their record | Alumni portals, events and careers services | Lower assurance; no institutional email |
For most institutions the separate scope or external identity models are safer: they take tens of thousands of rarely monitored accounts out of the directory that holds staff and research data.
Implementation: a phased rollout
- Inventory the current state (weeks 1 to 4): export every account with an affiliation, last sign-in date and the student record status behind it. Count accounts whose status is withdrawn, graduated or unknown but which can still sign in. This number is the baseline.
- Agree the state model and policy (weeks 4 to 8): sign off states, grace periods and the alumni model with registry, alumni relations, data protection and IT. Put grace periods in the retention schedule so they carry an end date.
- Map status codes to states: build the mapping table from student record codes to identity states, with a default of "no access" for unmapped codes.
- Automate in report-only mode: run the rules for one term without enforcing them and compare the computed state with the live state for every account. Investigate mismatches; most reveal missing codes or dual-role cases.
- Pilot one transition: enforce interruption and withdrawal first, which are smaller in volume than graduation. Keep a manual override list with expiry dates for exceptions.
- Enforce graduation and alumni rules: announce export deadlines to students well before the window ends, then run the transition after conferral. Disable before deleting, so a mistake can be reversed within the platform's restore window.
- Clean up the backlog: apply the rules to historical accounts in batches, using an inactivity threshold agreed in policy (Microsoft's guidance gives 18 months without sign-in as an example), and validate after each batch.
- Roll back safely: if a batch disables the wrong accounts, re-enable from the disabled state and fix the mapping, rather than restoring deleted accounts. This is why the disabled state comes before deletion.
Decision guidance
- Small colleges and schools: use the hard stop model with a clear export window, and run lifecycle rules from the platform's own tools. Avoid offering email for life unless there is budget to secure it.
- Large universities: use an identity governance platform or lifecycle workflow engine driven by the student record system, with a separate alumni scope. Invest in dual-role handling, since students who are also staff are common.
- Research-intensive institutions: postgraduate researchers often hold research data, cloud accounts and service credentials. Add an exit step that transfers ownership of datasets, repositories and any service accounts or API keys before the account is disabled. See the Contractor Identity Lifecycle Guide for comparable patterns.
- Schools with under-18s: account decisions may involve parents or guardians and safeguarding staff; take advice on local rules before setting suspension and deletion policies. See Student and University Cyber Safety for the student-facing view.
Detection and measurement
Lifecycle failures are silent: nothing alerts when a graduate keeps access. Build reports that look for state drift.
| What to monitor | Data source | Why |
|---|---|---|
| Accounts that can sign in whose student record status is withdrawn, graduated or unknown | Directory joined to student record extract | Primary measure of lifecycle drift |
| Sign-ins to accounts in disabled-pending or alumni states from new countries or devices | Identity provider sign-in logs | Dormant student accounts are attractive for spraying and resale |
| Federation attribute releases of student or member for identities not in an active state | Identity provider attribute release logs | Licensed resource access beyond entitlement |
| Manual overrides past their expiry date | Override register | Exceptions that became permanent |
| Identifier reuse attempts | Account creation logs | Recycled addresses inherit mail and resets |
Metrics
- Lifecycle drift: number of active accounts with no matching active student, staff or alumni state. Target zero after clean-up.
- Transition latency: median time from a status change in the student record to the identity change. Target under 24 hours.
- Grace period compliance: percentage of graduate accounts disabled by the end of the published window.
- Deletion on schedule: percentage of identities deleted within 30 days of their retention end date, with evidence.
- Override hygiene: number of manual overrides without an expiry date or past it.
Data protection and retention
Under UK GDPR Article 5(1)(e), personal data must be kept in an identifiable form for no longer than necessary. The ICO expects organisations to set their own retention periods, document them in a retention schedule, review data at the end of each period and delete or anonymise what is no longer needed, including in backups; moving data offline is not deletion. The ICO notes its guidance is under review following the Data (Use and Access) Act, so check for updates. In the United States, FERPA (20 U.S.C. 1232g, regulations at 34 CFR Part 99) gives rights over education records to eligible students, meaning students aged 18 or over or attending a postsecondary institution. See the FERPA Guide for Security Teams and the Data Retention and Secure Deletion Guide.
The practical consequence: the identity lifecycle and the records retention schedule must be the same document, or at least reference each other. An account deleted before its records are archived loses evidence; an account kept after the schedule says delete is a compliance finding.
Framework mapping
| Lifecycle control | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | ISO/IEC 27001:2022 Annex A | CIS Controls v8.1 |
|---|---|---|---|---|
| Identity creation and proofing at enrolment | PR.AA-01 | IA-12, AC-2 | A.5.16 Identity management | Control 5 Account Management |
| Role and entitlement changes per state | PR.AA-05 | AC-2 | A.5.18 Access rights | Control 6 Access Control Management |
| Disabling on withdrawal, graduation and inactivity | PR.AA-01 | AC-2(3) | A.5.18 Access rights | Control 5 Account Management |
| Retention and deletion of identity data | ID.AM-07 | SI-12 | A.8.10 Information deletion | Control 3 Data Protection |
| Lifecycle policy | GV.PO-01 | AC-2 | A.5.15 Access control | Control 5 Account Management |
Common failure patterns
- Graduation by spreadsheet: a yearly export of graduates is processed by hand, so late awards, resits and appeals are missed and accounts stay active for years.
- Unmapped status codes: new student record codes (for example a new interruption type) are added without an identity mapping, and the default is to keep access.
- Alumni treated as members: the identity provider keeps releasing member or student for graduates, so publisher and research services continue to grant licensed access.
- Dual-role collapse: when a student who is also employed graduates, the staff account is disabled as well, or the student entitlements survive because the staff role keeps the account alive.
- Recycled identifiers: a common name is reissued to a new student, who then receives mail and password reset messages meant for the previous holder.
- Re-created accounts: accounts deleted in the cloud directory return on the next sync because they were never disabled at the on-premises source.
Practitioner checklist
- Publish a state model from applicant to deleted, with the entitlements for each state.
- Map every student record status code to a state, defaulting unmapped codes to no access.
- Keep applicant accounts outside the main directory and proof identity at enrolment.
- Drive eduPersonAffiliation release from lifecycle state, and stop releasing member for alumni.
- Set enforced end dates for every grace period and record them in the retention schedule.
- Choose an alumni model and, for large programmes, move alumni into a separate scope.
- Run lifecycle rules in report-only mode for a term before enforcing them.
- Never reassign usernames, email addresses or persistent identifiers.
- Report weekly on lifecycle drift, transition latency and expired overrides.
- Transfer research data, repositories and service credentials before disabling researcher accounts.
Standards and references
- REFEDS: eduPerson (202111)
- NIST: SP 800-63A-4 Digital Identity Guidelines, Identity Proofing and Enrollment
- ICO: Principle (e), Storage Limitation
- US Department of Education: What is FERPA?
- Google Workspace Admin Help: Let Graduating Students Transfer Data
- Google Workspace Admin Help: Suspend a User Temporarily
- Microsoft Learn: Academic Year Transition, User Identities
- Microsoft Support: Manage Graduating Student Licenses and Content in Microsoft 365 Education
Related NHI Mgmt Group resources: Education Identity Security Guide · Cybersecurity for Higher Education Guide · Student and University Cyber Safety · Joiner-Mover-Leaver Guide