The Módulo de Registro de Vacaciones is a web-based HR tool that helps organizations manage the full vacation lifecycle for their employees. From registering new staff and calculating their vacation entitlement, to scheduling individual periods, visualizing usage, rescheduling expiring ranges, and maintaining official ESINAD documentation identifiers — everything is handled in one place.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CKoldo/Vacaciones-front/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
Get the system running in under 5 minutes
Authentication
Log in and understand role-based access
Core Modules
Explore all five functional modules
API Reference
Integrate with the backend REST API
What you can do
Register employees
Add employees with their hire date to automatically calculate vacation period eligibility.
Schedule vacations
Create flexible (1–7 day) or block (7+ day) vacation ranges for each employee.
Visualize usage
See a per-employee summary of days taken, days remaining, and regulatory alerts.
Reschedule ranges
Move expiring vacation ranges to new dates while preserving the full audit history.
Administer ESINAD IDs
Assign and manage official ESINAD document identifiers on each vacation range.
Export reports
Download vacation data as Excel (.xlsx) or PDF for reporting and compliance.
Key concepts
Before diving into the modules, it helps to understand the vacation rules built into the system:- Vacation period: each employee earns 30 days per year, starting one year after their hire date
- Flexible days: up to 7 days can be taken in short ranges (1–7 consecutive days)
- Block days: the remaining 23 days must be taken in a single block of 7 or more consecutive days
- Friday rule: selecting a Friday as a start or end date automatically extends the range through the weekend
- Advance vacations: employees can borrow days from a future period when the current one is exhausted
The system connects to a backend REST API. Make sure the API server is running and the
VITE_API_URL environment variable is set before starting the front end.