Employee Document Versioning · How-to guide

Withdraw an employee document version

Mark the current v1.3.0 document/version withdrawn with a reason without deleting its file or history. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: HR administrators and authorised managersPermission: Human Resource Management: EditModule v1.3.0
Jump to steps
Where to go Admin Area → Human Resources → Employee Record Centre → Select employee → Documents → Withdraw
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.

What you need before you start

  • Access to Admin Area → Human Resources → Employee Record Centre → Select employee → Documents → Withdraw.
  • The Human Resource Management: Edit capability or administrator access.
  • The correct employee, record, period or authorised evidence.

How to do it

  1. Go to the current document.
  2. Click Withdraw.
  3. Enter the required withdrawal reason.
  4. Verify the withdrawal.
  5. Check the current version status is Withdrawn and history remains available.

What the module checks

  • Withdrawal is not deletion.
  • The reason and staff action are audited.
  • A withdrawn document can be restored through the provided Restore action.

What happens next

The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it.

Troubleshooting

  • If the control is missing, confirm the required HRM permission and module version 1.3.0.
  • If saving fails, correct the exact field or state named in the validation message.
  • If an email/automation is missing, review the module delivery/audit log and host cron/mail settings.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: employee document versioning