Events are the core objects in UniEvents. Each event belongs to a faculty tenant, occupies a physical space for a defined duration, and can be made public or restricted to direct-link access. BothDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/Edfermachado/proyectoSistemas/llms.txt
Use this file to discover all available pages before exploring further.
tenant_admin and event_manager roles can create events, but their default status and publication flow differ. This guide walks through the full creation process, status lifecycle, and advanced options available from the faculty admin portal.
Creating an Event
Navigate to the new event form
Go to
/faculty-admin/events/new. The form will automatically detect your faculty’s tenantId from the active session — you do not need to enter it manually.Fill in the core event details
Complete the following required fields:
| Field | Type | Notes |
|---|---|---|
title | string | The event’s display name. |
description | string (optional) | Full description shown on the event page. |
date | datetime | Start date and time. Cannot be set in the past. |
duration | integer (minutes) | Event length. Must be between 1 and 1440 minutes (24 hours). |
spaceId | select | Physical venue from your faculty’s registered spaces. Required. |
capacity | integer (optional) | Override the space’s physical capacity with an event-specific limit. When set, this value completely replaces the space’s capacity for registration enforcement. |
Set event visibility
Choose one of two visibility options from the Visibilidad dropdown:
publico— the event appears in the public discovery feed and on the university’s home page carousel (if featured).privado— the event is accessible only via a direct link; it does not appear in public listings.
Configure pricing
Enter the admission price in the Precio de Entrada field. Use
Attendees will use these details to submit their payment reference and screenshot when registering for a paid event.
0 or check the Es Gratis toggle to mark the event as free.If the event is paid, you must also fill in the mobile payment details:| Field | Description |
|---|---|
paymentPhone | The mobile payment phone number (e.g. 0414-1234567). |
paymentId | The national ID or tax ID (cédula/RIF) associated with the payment account. |
paymentBank | The receiving bank, selected from the Venezuelan banking system list. |
Assign an event manager
Select a Encargado del Evento (event manager) from the
managerId dropdown. This must be a user with the event_manager role within your faculty. The field is required.Upload an event image (optional)
Upload a banner or cover image for the event. Accepted formats: JPG, PNG, WebP. Maximum file size: 5 MB.
Uploaded images are automatically processed using the
sharp library — resized to 1200×800 pixels (cover fit, without upscaling) and converted to WebP at quality 80 before being stored in Supabase storage. The stored URL is saved to imageUrl on the event record.Event Status
Every event has astatus field that controls its visibility and availability:
| Status | Meaning |
|---|---|
pendiente | The event has been proposed by an event_manager and is awaiting review by a tenant_admin. |
aprobado | The event is published and visible to attendees (if public). Attendee management is unlocked. |
rechazado | The event has been rejected. It remains in the system but is not published. |
tenant_admin can approve a pendiente event directly from the /faculty-admin/events table by clicking the checkmark (✓) action button beside the event row. This calls a server action that updates status to aprobado and revalidates the events page.
Space Conflict Detection
UniEvents prevents double-booking of physical spaces. When submitting a new event (or editing an existing one), theEventsService.checkSpaceConflict method checks whether the selected space is already occupied during the event’s time window.
The conflict window is calculated as:
newStart < existingEnd && existingStart < newEnd — the standard interval overlap condition.
If a conflict is detected, the API returns:
CONF_001 is the canonical identifier for a space scheduling conflict. The form will display this message inline so the admin can choose a different space or time slot.
Featured Events
tenant_admin users can set the isFeatured boolean flag on any aprobado event. Featured events appear in the home page carousel for the university’s public discovery experience.
isFeatured can be toggled via PUT /api/events/[id] with { "isFeatured": true }.
IP Protection
Enabling the Requiere Protección Intelectual (IP) checkbox setsrequiresIpProtection: true on the event. This flag is intended to restrict display of sensitive event details and is respected by the front-end rendering layer to conditionally hide content.
API Reference — Creating an Event
Events are submitted asmultipart/form-data to allow image uploads alongside the event metadata.
201 Created):