HRMS · Leave
Route /admin/leave/document-rules · /admin/leave/document-review · /admin/leave/document-retention

Leave Documents

Register view for document rules, review queues, and retention — create/update via forms when available, or API.

Register view — create/update via forms when available, or API. Flowcharts: rule → upload → review → retain.

Evidence on leave

Rules, review queue, and retention for attachments

Leave documents is document rules, review queues, and retention for leave evidence. Create/update via forms when available, or API. Medical and similar files follow masking and retention — not a public drive.

Admin → Leave documents Route /admin/leave/document-rules HR Admin · Org Admin

The job of this console

Set when a type needs a document, review what employees attached, and honor retention. Do not copy medical files into Work Graph or AI logs.

Seat at the table

HR administrators. Employees attach from Leave management when the rule says so. Managers may see status, not necessarily the file.

The working rhythm

Open rules, adjust a type, then work the review queue. Apply retention; do not download a personal archive to email.

Moments that bring you here

A type that should require a certificate. A backlog of unreviewed files. Retention expiry. A subject-access request.

ⓘ
Sensitive attachments
Persona masking and retention apply. Do not persist raw medical content in search snippets or audit metadata.

Flowcharts

Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.

1 — Evidence required path

When document rules block submit until evidence exists.

flowchart TD
  A[Apply leave] --> R{Docs required?}
  R -->|No| Sub[Submit]
  R -->|Yes| U[Upload evidence]
  U --> Rev[Review]
  Rev --> Sub
            
  1. 1
    Apply leaveEmployee selects type needing evidence.
  2. 2
    Docs required?Document rules for that type/duration.
  3. 3
    Upload evidenceEmployee attaches files in the request flow.
  4. 4
    ReviewHR accepts or requests resubmission.
  5. 5
    SubmitRequest proceeds to approval when rules pass.

2 — Retention

Accepted documents move to retention schedule.

flowchart TD
  Acc[Accepted doc] --> Ret[Retention rule]
  Ret --> Keep[Keep until date]
  Keep --> Purge{Expired?}
  Purge -->|Yes| Del[Purge / anonymize]
  Purge -->|No| Keep
            
  1. 1
    Accepted docPassed document review.
  2. 2
    Retention ruleType-specific keep period.
  3. 3
    Keep until dateStored with access controls.
  4. 4
    Expired?Past legal/HR retention window.
  5. 5
    Purge / anonymizeRemove or mask per policy.

Overview

Document rules, review, and retention keep medical and legal evidence on a controlled lifecycle. These screens are primarily registers; create/update via forms when available, or API.

How to use

1. Open document rules
Admin → Leave → Document rules register.
2. Review or update rules
Create/update via forms when available, or API.
3. Document review queue
Inspect pending reviews; act via forms when available, or API.
4. Retention register
Inspect retention rows; schedule changes via forms when available, or API.