Skip to content
Education Host

Student web hosting

What happens to student websites after a course ends?

By Education HostPublished Updated

Student websites need an agreed lifecycle after teaching ends. Decide separately what happens to the live site, student access, assessment evidence, archives and backup copies. Record owners, review dates, exceptions and an export route before changing access or deleting anything. Suspension is an access-control action, not proof of a usable archive or a verified backup; retention and recovery depend on institutional policy and the configured service.

How are restriction, suspension, archiving and deletion different?

Treat them as separate actions with separately tested effects. A dashboard label does not establish who can log in, whether a website remains public, what data is held or how recovery works.

Lifecycle actions: intended purpose and evidence to check
ActionPurposeCheck before relying on it
Restrict changes or accessApply agreed controls during teaching or assessmentTest logins, uploads, application writes and public pages; confirm assessors can still use the work
Suspend an accountStop configured account services while retaining the account for an agreed purposeConfirm service behaviour, authorised reopening, continuing charges and suspended-account backup coverage
Archive required materialRetain specified content outside the active teaching estateCheck files and databases included, access controls, formats, retrieval test, owner and review/expiry date
Delete an account or copyRemove material no longer required under the agreed policyCheck holds, exceptions, approval, exports and the handling of live, archive and backup copies

What should an institutional account-retention policy record?

Record the purpose, owner, trigger, review point and evidence needed for each decision. This matrix is a planning template: institutional assessment, records and data-protection teams agree the actual controls and periods. A teaching end date alone is not a complete retention policy.

Illustrative student-hosting policy matrix: agree local dates and approvals
SituationExample ownerDecision and evidence to record
Submission and markingAssessment leadRequired assessment copy, deadline, examiner access and tested change restrictions; preserve the submission independently of the live site
Resit, extension or interruptionAuthorised academic approverAccounts affected, reason, permitted access, revised end/review date and original evidence to preserve
Graduate portfolio exportCourse and hosting service ownersNotice and export route before access expires, destination ownership and separately agreed continuation
Group project closureModule leadAuthorised recipients, shared-content permissions, member notification and the assessment record retained
Assessment or records holdRelevant institutional records ownerMaterial covered, controlled access, reason for the hold and a named review/decision point
Expiry and deletionRecords-policy and service ownersNo outstanding hold or approved exception, notice/export status, authorisation and handling of retained copies

How do you preserve coursework without depending on the live site?

Capture the material assessment needs and test that an authorised assessor can use it. A changing public website, a server backup and an assessment submission serve different purposes; none should silently stand in for another.

  • Agree whether the assessment record needs site files, a database export, uploads, source code, screenshots or other submission artefacts.
  • Record the account/module, submission point, relevant software versions and who may access the preserved copy.
  • Test the preserved work in the intended marking workflow, including an application that depends on its database.
  • Preserve the original submission before reopening an environment for a resit or extension; record which copy is being assessed.

Read next: Student website backups, resets and recovery

Are suspended accounts automatically backed up and cheap to retain?

Neither should be assumed. Suspension changes access or services; it does not prove backup coverage, recoverability or a reduction in charges. Storage, licences, backup copies and administration may still be needed while an account is inactive.

cPanel documents that automated WHM backups exclude suspended accounts by default unless the relevant setting is enabled. Your provider may use a different backup arrangement. Ask what actually covers the accounts, whether the relevant backups succeeded and whether a representative restore has been tested. A named setting is not a reason to change a live backup policy without reviewing its scope.

Read next: Include retained accounts and recovery in the budget

What should students check before exporting a website?

Give students a documented export route before access expires and explain what it includes. Test a representative export in an authorised destination: moving a dynamic website can require software, path, domain and database changes. A download existing is not evidence that the project works elsewhere.

  • Identify site files, uploads and the database export; confirm the selected download includes the required material.
  • Record software/runtime versions and non-secret setup instructions needed to use the project elsewhere.
  • Agree who may receive group or client-project material; an account does not settle permissions for everything inside it.
  • Use an approved transfer route. Keep passwords, keys and participant data out of a general support enquiry.
  • Confirm receipt or record transfer exceptions before the agreed irreversible closure step.

Read next: Portfolio and client-project hosting after teaching

How should resits, extensions and returning students be handled?

Use an approved exception record with the account, reason, authoriser, permitted access and review/end date. Check which account or copy should be reopened and preserve the original assessment evidence first. A request to reopen does not establish that the needed archive or backup still exists.

For returning students, review module membership, software compatibility and the data still needed before restoring access. Record the result so the next rollover respects the exception. Withdrawal, interruption and return arrangements follow institutional policy rather than a universal hosting rule.

How should live, archive and backup retention be coordinated?

Set retention by purpose and applicable institutional requirements, with records and data-protection input. ICO guidance does not prescribe one period for every category of personal data. Live accounts, assessment archives and operational backups may have different purposes and controls; document their schedules instead of assuming identical expiry dates.

Agree what happens if a live account is deleted while a copy remains in a justified backup cycle. Record access restrictions, expiry or removal arrangements and controls against restoring deleted material into ordinary use. Ask the provider to explain the configured process; do not promise instant removal from every copy or recovery after expiry.

What must be checked before irreversible deletion?

Use an approval gate based on the agreed policy, not only a scheduled date. This operational checklist does not determine retention periods.

  • Reconcile the proposed account/cohort action list against current enrolment and approved exceptions.
  • Check for assessment, appeal, records or other authorised holds with the relevant institutional owner.
  • Confirm required assessment material is preserved and usable by authorised staff.
  • Check the agreed student/member notices, export route and outstanding transfer exceptions.
  • Record approval, the material being removed and the configured treatment of archives and backups.
  • Review operation results and failures, retain the appropriate action record and remove obsolete access through the agreed process.

Read next: Plan cohort launch and lifecycle responsibilities together

What does Student Web Host Manager contribute?

Student Web Host Manager provides institutional account management with courses, modules, teaching blocks, role-based visibility, a suspension manager, lifecycle states and bulk actions. These tools support an agreed lifecycle; they do not choose retention periods or establish that every archive, backup and export meets assessment needs.

Confirm state transitions, authorised roles, identity configuration, notices, recovery and exceptions during scoping and testing. The institution retains policy decisions; the agreed service scope identifies operational tasks for Education Host and institutional staff.

Sources and further reading

Primary sources supporting the guidance in this article.

  • ICO: storage limitation

    Retention must be justified for the relevant purpose; no universal UK GDPR period is prescribed for student websites.

  • cPanel: manage account suspension

    Suspension and termination are different operations. Test the configured access and serving behaviour before relying on a restriction for assessment.

  • cPanel: enable backups for suspended accounts

    Automated WHM backups omit suspended accounts by default unless the relevant setting is enabled. Confirm the actual backup service and recovery tests.

Suspending, archiving and deleting accounts — frequently asked questions

Short, self-contained answers that complement the guide above.

Should student accounts be deleted when teaching ends?

Not solely because teaching has ended. Apply the agreed assessment and retention process, check holds and exceptions, preserve required evidence and complete notices and exports. The eventual deletion decision needs a defined purpose, approval and handling of retained copies.

Does suspension make a coursework site read-only for marking?

Do not assume so. Suspension may stop public serving or the logins an examiner needs. Test the configured restriction and assessment workflow, and preserve required submission evidence separately from the live site.

Can archived student work always be restored?

Recovery depends on what was retained, its format, software compatibility, retention period and the configured restore process. Confirm and test a representative retrieval; an archived label alone is not a recovery guarantee.

Are suspended cPanel accounts included in backups?

Not automatically in the default automated WHM backup configuration: cPanel documents a separate setting for suspended-account backups. Confirm the actual service and recovery tests for the institutional deployment, which may use a different arrangement.

Do all backup copies disappear immediately when an account is deleted?

Do not assume immediate removal. Agree retention, access, expiry or deletion for operational backups, archives and live accounts, including controls against restoring deleted material into ordinary use. Ask the provider to explain the configured process.

How long should student coursework be retained?

Use institutional assessment, records and data-protection decisions for the material and its purpose. There is no universal hosting retention period. Record owners, triggers, review/expiry decisions and exceptions for live accounts, assessment evidence and retained copies.

Talk to Education Host

Questions this guide didn't answer?

Tell us about your modules, cohorts and constraints — we will answer the technical and commercial questions honestly, including where a cloud lab is not the right fit.