Personnel Management API

The Personnel API provides comprehensive endpoints for managing staff members, including registration, profile updates, role assignments, operational assignments, and access control. This module enforces labor status validation, tracks absence history, and maintains full audit trails for all personnel changes.

Permissions

All personnel endpoints require authentication and specific permissions:

VIEW_STAFF - Required for viewing personnel data
MANAGE_STAFF - Required for creating, updating, and managing staff
ASSIGN_OPERATIONS - Required for assigning personnel to operational tasks

Get All Staff

curl -X GET https://api.prod-sys.com/api/personal \
  -H "Authorization: Bearer YOUR_TOKEN"

GET /api/personal

{
  "success": true,
  "data": [
    {
      "id": 1,
      "nombre": "Juan",
      "apellido": "Pérez",
      "codigo_interno": "EMP001",
      "area_id": 2,
      "area_nombre": "Producción",
      "email": "[email protected]",
      "telefono": "+52-555-1234",
      "fecha_ingreso": "2024-01-15",
      "rol_organizacional": "Técnico de Línea",
      "estado_laboral": "Activo",
      "rol_actual": "Operario",
      "username": "EMP001",
      "estado_usuario": "Activo",
      "estado_efectivo": "Activo",
      "ausencia_vencida": false,
      "es_auxiliar_activo": false,
      "created_at": "2024-01-15T10:30:00Z",
      "updated_at": "2024-01-15T10:30:00Z"
    }
  ]
}

Authorization

Required Permission: VIEW_STAFF

Response Schema

Returns an enriched list of all personnel with computed state information:

success

boolean

required

Indicates if the request was successful

data

array

required

Array of personnel objects

integer

Unique personnel identifier

nombre

string

First name

apellido

string

Last name

codigo_interno

string

Internal employee code (also used as username)

area_id

integer

Foreign key to areas table

area_nombre

string

Area name (e.g., “Producción”, “Administración”)

string

Email address

telefono

string

Phone number

fecha_ingreso

string

Date of hire (YYYY-MM-DD format)

rol_organizacional

string

Organizational role title

estado_laboral

string

Current labor status. One of: Activo, Incapacitado, Inactivo, Baja

rol_actual

string

Current system role name

username

string

estado_usuario

string

User account status: Activo or Inactivo

estado_efectivo

string

Computed effective status. Automatically reverts to Activo if absence period has expired

ausencia_vencida

boolean

Indicates if the absence period has expired and auto-reactivation occurred

es_auxiliar_activo

boolean

Whether this person is an active auxiliary (Auxiliar operational role + Activo state)

ausencia_desde

string

Start date of current absence (YYYY-MM-DD)

ausencia_hasta

string

End date of current absence (YYYY-MM-DD)

tipo_ausencia

string

Type of absence: Incapacidad or Permiso

motivo_ausencia

string

Reason for absence

Business Logic

Auto-Reactivation: Staff with expired absence periods (ausencia_hasta < today) are automatically transitioned back to Activo status
State Enrichment: The response includes both estado_laboral (stored) and estado_efectivo (computed)
Audit Trail: Auto-reactivations are logged with reason "Retorno automático por vencimiento de ausencia"

Get Staff Details

curl -X GET https://api.prod-sys.com/api/personal/1 \
  -H "Authorization: Bearer YOUR_TOKEN"

GET /api/personal/:id

{
  "success": true,
  "data": {
    "id": 1,
    "nombre": "Juan",
    "apellido": "Pérez",
    "codigo_interno": "EMP001",
    "area_nombre": "Producción",
    "email": "[email protected]",
    "telefono": "+52-555-1234",
    "fecha_ingreso": "2024-01-15",
    "rol_organizacional": "Técnico de Línea",
    "estado_laboral": "Activo",
    "estado_efectivo": "Activo",
    "rol_actual": "Operario",
    "username": "EMP001",
    "estado_usuario": "Activo",
    "historial_roles": [
      {
        "id": 5,
        "persona_id": 1,
        "rol_id": 3,
        "rol_nombre": "Operario",
        "asignado_por": 2,
        "asignado_por_nombre": "María López",
        "motivo_cambio": "Registro inicial de personal y usuario",
        "fecha_asignacion": "2024-01-15T10:30:00Z",
        "activo": 1
      }
    ],
    "asignaciones_activas": [
      {
        "id": 12,
        "persona_id": 1,
        "proceso_id": 101,
        "proceso_nombre": "Ensamble Final",
        "maquina_id": 7,
        "maquina_codigo": "MAQ-007",
        "turno": "T1",
        "permanente": false,
        "fecha_inicio": "2024-03-01T08:00:00Z",
        "fecha_fin": null,
        "created_by": 2
      }
    ],
    "rol_operativo_actual": {
      "id": 8,
      "persona_id": 1,
      "rol_operativo_id": 2,
      "rol_nombre": "Operador Especializado",
      "fecha_desde": "2024-02-01T00:00:00Z",
      "fecha_hasta": null,
      "motivo": "Promoción por desempeño",
      "asignado_por": 2
    },
    "historial_grupos": [
      {
        "id": 3,
        "grupo_id": 1,
        "grupo_nombre": "Grupo A - Turno 1",
        "persona_id": 1,
        "fecha_desde": "2024-01-20T00:00:00Z",
        "fecha_hasta": null,
        "motivo": "Asignación operativa estándar",
        "asignado_por": 2
      }
    ],
    "historial_ausencias": [
      {
        "id": 1,
        "persona_id": 1,
        "estado_laboral": "Incapacitado",
        "tipo_ausencia": "Incapacidad",
        "ausencia_desde": "2024-02-10",
        "ausencia_hasta": "2024-02-15",
        "motivo_ausencia": "Incapacidad médica temporal",
        "registrado_por": 2,
        "fecha_registro": "2024-02-10T09:00:00Z"
      }
    ]
  }
}

Parameters

integer

required

Personnel ID

Authorization

Required Permission: VIEW_STAFF

Response Schema

Returns comprehensive personnel details including all related history:

success

boolean

required

Request success indicator

data

object

required

Detailed personnel information

historial_roles

array

Complete history of system role assignments

asignaciones_activas

array

Active operational assignments (process + machine assignments)

rol_operativo_actual

object

Current operational role (e.g., “Operador Especializado”, “Auxiliar”)

historial_grupos

array

History of group memberships

historial_ausencias

array

Complete absence history with reasons and dates

Register Staff

curl -X POST https://api.prod-sys.com/api/personal \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "nombre": "Ana",
    "apellido": "García",
    "codigo_interno": "EMP015",
    "area_id": 2,
    "email": "[email protected]",
    "telefono": "+52-555-5678",
    "fecha_ingreso": "2024-03-01",
    "rol_organizacional": "Operador de Máquina"
  }'

{
  "nombre": "Ana",
  "apellido": "García",
  "codigo_interno": "EMP015",
  "area_id": 2,
  "email": "[email protected]",
  "telefono": "+52-555-5678",
  "fecha_ingreso": "2024-03-01",
  "rol_organizacional": "Operador de Máquina"
}

{
  "success": true,
  "data": {
    "id": 15,
    "tempPassword": "x9k2m5p8"
  },
  "message": "Personal registrado correctamente. Se ha generado una contraseña temporal."
}

Authorization

Required Permission: MANAGE_STAFF

Request Body

nombre

string

required

First name (minimum 1 character)

apellido

string

required

Last name (minimum 1 character)

codigo_interno

string

required

Unique internal employee code. Will be used as the username. Must not already exist in the system.

area_id

integer

required

Area ID (must be a valid area from the areas catalog)

string

Email address. Must be unique if provided.

telefono

string

Phone number

fecha_ingreso

string

Date of hire in YYYY-MM-DD format

rol_organizacional

string

required

Organizational role title (minimum 1 character)

Response Schema

success

boolean

required

Request success indicator

data

object

required

integer

ID of the newly created personnel record

tempPassword

string

Temporary password generated for the user account. In production, this should be sent via secure email only.

message

string

required

Success message

Business Logic

Uniqueness Validation: The system validates that both codigo_interno and email are unique
Automatic User Account: A user account is automatically created with:
- Username = codigo_interno
- Auto-generated temporary password (8 characters)
- Default role: “Operario” (or first available role)
- must_change_password flag set to true
Transaction Safety: The entire operation runs within a database transaction
Audit Trail: Creation is logged with reason “Registro inicial de personal y usuario”
Password Security: Passwords are hashed using bcrypt with 10 rounds

In production environments, the temporary password should only be sent via secure email. The password is included in the response for development purposes only.

Error Responses

{
  "success": false,
  "error": "El código interno ya está registrado"
}

Update Staff

curl -X PUT https://api.prod-sys.com/api/personal/15 \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "telefono": "+52-555-9999",
    "estado_laboral": "Incapacitado",
    "ausencia_desde": "2024-03-15",
    "ausencia_hasta": "2024-03-22",
    "tipo_ausencia": "Incapacidad",
    "motivo_ausencia": "Incapacidad médica por cirugía menor",
    "motivo_cambio": "Actualización de estado por incapacidad médica"
  }'

{
  "telefono": "+52-555-9999",
  "estado_laboral": "Incapacitado",
  "ausencia_desde": "2024-03-15",
  "ausencia_hasta": "2024-03-22",
  "tipo_ausencia": "Incapacidad",
  "motivo_ausencia": "Incapacidad médica por cirugía menor",
  "motivo_cambio": "Actualización de estado por incapacidad médica"
}

{
  "success": true,
  "message": "Personal actualizado correctamente."
}

Parameters

integer

required

Personnel ID to update

Authorization

Required Permission: MANAGE_STAFF

Request Body (All fields optional)

nombre

string

First name

apellido

string

Last name

string

Email address

telefono

string

Phone number

area_id

integer

Area ID

rol_organizacional

string

Organizational role title

estado_laboral

string

Labor status. One of: Activo, Incapacitado, Inactivo, Baja

ausencia_desde

string

Start date of absence (YYYY-MM-DD). Required when estado_laboral is Incapacitado, Inactivo, or Baja

ausencia_hasta

string

End date of absence (YYYY-MM-DD). Required for Incapacitado and Inactivo. Must be null for Baja

tipo_ausencia

string

Type of absence: Incapacidad or Permiso. Must match estado_laboral constraints

motivo_ausencia

string

Reason for absence (minimum 5 characters). Required for all non-Activo states

motivo_cambio

string

required

Reason for the update (minimum 5 characters). Required for audit trail

categoria_motivo

string

Category of the change reason for audit classification

Business Logic

Terminal State Protection

Staff with estado_laboral = "Baja" cannot be modified. Returns error: “Estado terminal: No se pueden realizar cambios en un colaborador dado de Baja”

Estado Laboral Rules

Incapacitado:

Requires: ausencia_desde, ausencia_hasta, tipo_ausencia = "Incapacidad", motivo_ausencia
System validates that tipo_ausencia is “Incapacidad”

Inactivo:

Requires: ausencia_desde, ausencia_hasta, tipo_ausencia = "Permiso", motivo_ausencia
System validates that tipo_ausencia is “Permiso”

Baja:

Requires: ausencia_desde, motivo_ausencia
System automatically sets: ausencia_hasta = null, tipo_ausencia = null
This is a terminal state - no further modifications allowed

Activo:

System automatically clears all absence fields: ausencia_desde, ausencia_hasta, tipo_ausencia, motivo_ausencia = null

Audit Trail

All changes are logged to the audit system
State changes trigger logStatusChange
Other updates trigger logUpdate with before/after comparison
Absence history is saved to historial_ausencias table for non-Activo transitions

Error Responses

{
  "success": false,
  "error": "Estado terminal: No se pueden realizar cambios en un colaborador dado de Baja"
}

Assign Role

curl -X POST https://api.prod-sys.com/api/personal/15/rol \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "rol_id": 5,
    "motivo_cambio": "Promoción a supervisor de línea",
    "es_correccion": false,
    "categoria_motivo": "Promoción"
  }'

{
  "rol_id": 5,
  "motivo_cambio": "Promoción a supervisor de línea",
  "es_correccion": false,
  "categoria_motivo": "Promoción"
}

{
  "success": true,
  "message": "Rol asignado correctamente."
}

Parameters

integer

required

Personnel ID

Authorization

Required Permission: MANAGE_STAFF

Request Body

rol_id

integer

required

System role ID to assign. Must be a valid role from the roles catalog.

motivo_cambio

string

required

Reason for the role change (minimum 5 characters). Required for audit trail.

es_correccion

boolean

default:"false"

Mark this change as a correction. If true, “[CORRECCIÓN]” prefix is added to motivo_cambio.

categoria_motivo

string

Category of the change reason for audit classification

Business Logic

Terminal State Protection: Cannot assign roles to staff with estado_laboral = "Baja"
Transaction Safety: Role assignment runs within a database transaction
Historical Tracking:
- Previous role assignment is deactivated (activo = 0)
- New role assignment is inserted into persona_roles table with activo = 1
- Current role in usuarios table is updated
Audit Trail: Comprehensive audit log created with action ROLE_CHANGE
Correction Support: If es_correccion = true, the motivo is prefixed with “[CORRECCIÓN]“

Error Responses

{
  "success": false,
  "error": "Persona no encontrada"
}

Reset Password

curl -X PUT https://api.prod-sys.com/api/personal/15/reset-password \
  -H "Authorization: Bearer YOUR_TOKEN"

{
  "success": true,
  "data": {
    "tempPassword": "m3n9k5x2"
  }
}

Parameters

integer

required

Personnel ID

Authorization

Required Permission: MANAGE_STAFF

Response Schema

success

boolean

required

Request success indicator

data

object

required

tempPassword

string

Newly generated temporary password (8 characters)

Business Logic

Password Generation: System generates a random 8-character alphanumeric password
Password Hashing: Password is hashed with bcrypt (10 rounds) before storage
Force Change: The must_change_password flag is automatically set to true
Audit Trail: Logged with action PASSWORD_RESET and reason “Reset de contraseña por administrador”
User Validation: Verifies that the person has an associated user account

In production environments, the temporary password should be sent to the user via secure email and not returned in the API response.

Assign Operation

curl -X POST https://api.prod-sys.com/api/personal/15/asignacion \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "proceso_id": 101,
    "maquina_id": 7,
    "turno": "T1",
    "permanente": false,
    "motivo_cambio": "Asignación temporal para cobertura de vacaciones",
    "es_correccion": false
  }'

{
  "proceso_id": 101,
  "maquina_id": 7,
  "turno": "T1",
  "permanente": false,
  "motivo_cambio": "Asignación temporal para cobertura de vacaciones",
  "es_correccion": false
}

{
  "success": true,
  "message": "Asignación operativa registrada correctamente."
}

Parameters

integer

required

Personnel ID to assign

Authorization

Required Permission: ASSIGN_OPERATIONS

Request Body

proceso_id

integer

required

Process ID to assign the person to. Must be a valid process from ProcessRegistry.

maquina_id

integer

Machine ID if the assignment is machine-specific. Machine must exist and not be in “Baja” or “Fuera de servicio” status.

turno

string

required

Shift identifier (e.g., “T1”, “T2”, “T3”, “T4”)

permanente

boolean

default:"false"

Whether this is a permanent assignment

motivo_cambio

string

Reason for the assignment (minimum 5 characters). Defaults to “Asignación operativa regular”

es_correccion

boolean

default:"false"

Mark this assignment as a correction. If true, “[CORRECCIÓN]” prefix is added.

categoria_motivo

string

Category of the assignment for audit classification

Business Logic

Assignment Validation

Personnel State Validation:
- Only staff with estado_laboral = "Activo" can be assigned
- Returns error: “Asignación bloqueada: El colaborador se encuentra en estado . Solo colaboradores en estado Activo pueden participar en la operación.”
User Account Validation:
- Personnel must have an associated user account
- Technical admin user cannot be assigned to operations
Machine Validation (if maquina_id provided):
- Machine must exist
- Machine cannot be in “Baja” or “Fuera de servicio” status
- Returns error: “Asignación bloqueada: La máquina se encuentra en estado .”
Transaction Safety: All validations and inserts run within a database transaction
Audit Trail: Logged with action OPERATIONAL_ASSIGNMENT including proceso_id, maquina_id, and turno

Error Responses

{
  "success": false,
  "error": "Asignación bloqueada: El colaborador se encuentra en estado Incapacitado. Solo colaboradores en estado Activo pueden participar en la operación."
}

Toggle Access

curl -X PUT https://api.prod-sys.com/api/personal/15/acceso \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "acceso_activo": false
  }'

{
  "acceso_activo": false
}

{
  "success": true,
  "data": {
    "acceso_activo": false
  }
}

Parameters

integer

required

Personnel ID

Authorization

Required Permission: MANAGE_STAFF

Request Body

acceso_activo

boolean

required

Whether to activate or deactivate system access

Business Logic

Area Restriction: This endpoint only works for personnel in the “Producción” area
Terminal State Protection: Cannot toggle access for staff with estado_laboral = "Baja"
User Validation: Verifies that the person has an associated user account
State Update: Updates estado_usuario in the usuarios table to “Activo” or “Inactivo”
Audit Trail: Logged with action TOGGLE_ACCESO showing before/after estado_usuario values

This feature is specifically designed for production floor personnel who may need temporary access suspension without changing their labor status.

Error Responses

{
  "success": false,
  "error": "El control de acceso por toggle solo aplica a personal de Producción"
}

Get Catalogs

curl -X GET https://api.prod-sys.com/api/personal/catalogos \
  -H "Authorization: Bearer YOUR_TOKEN"

{
  "success": true,
  "data": {
    "areas": [
      {
        "id": 1,
        "nombre": "Administración",
        "descripcion": "Personal administrativo y de oficina"
      },
      {
        "id": 2,
        "nombre": "Producción",
        "descripcion": "Personal de planta y operaciones"
      },
      {
        "id": 3,
        "nombre": "Calidad",
        "descripcion": "Control de calidad e inspección"
      },
      {
        "id": 4,
        "nombre": "Mantenimiento",
        "descripcion": "Mantenimiento preventivo y correctivo"
      }
    ],
    "roles": [
      {
        "id": 1,
        "nombre": "Administrador",
        "descripcion": "Acceso completo al sistema"
      },
      {
        "id": 2,
        "nombre": "Supervisor",
        "descripcion": "Supervisión de personal y operaciones"
      },
      {
        "id": 3,
        "nombre": "Operario",
        "descripcion": "Personal operativo de planta"
      },
      {
        "id": 4,
        "nombre": "Calidad",
        "descripcion": "Inspector de calidad"
      }
    ]
  }
}

Authorization

Required Permission: VIEW_STAFF

Response Schema

Returns reference catalogs used for personnel management:

success

boolean

required

Request success indicator

data

object

required

areas

array

List of organizational areas

integer

Area ID

nombre

string

Area name

descripcion

string

Area description

roles

array

List of system roles

integer

Role ID

nombre

string

Role name

descripcion

string

Role description

Usage

This endpoint provides the catalog data needed for:

Populating dropdown menus in personnel forms
Validating area_id and rol_id in other endpoints
Displaying human-readable area and role names

Get Operational Roles

curl -X GET https://api.prod-sys.com/api/personal/roles-operativos \
  -H "Authorization: Bearer YOUR_TOKEN"

{
  "success": true,
  "data": [
    {
      "id": 1,
      "nombre": "Auxiliar",
      "descripcion": "Personal de apoyo operativo",
      "activo": 1
    },
    {
      "id": 2,
      "nombre": "Operador Especializado",
      "descripcion": "Operador certificado en procesos específicos",
      "activo": 1
    },
    {
      "id": 3,
      "nombre": "Técnico",
      "descripcion": "Técnico de línea con competencias avanzadas",
      "activo": 1
    }
  ]
}

Authorization

Required Permission: VIEW_STAFF

Response Schema

Returns the list of operational roles (distinct from system roles):

success

boolean

required

Request success indicator

data

array

required

List of active operational roles

integer

Operational role ID

nombre

string

Role name

descripcion

string

Role description

activo

integer

Active status (1 = active, 0 = inactive)

Operational Roles vs System Roles

System Roles control permissions and access levels in the application (e.g., Administrador, Supervisor, Operario).Operational Roles define production floor responsibilities and competencies (e.g., Auxiliar, Operador Especializado, Técnico).A person can have one system role and one operational role simultaneously.

Data Models

Personnel Entity

Core personnel record stored in the personas table:

CREATE TABLE personas (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  nombre TEXT NOT NULL,
  apellido TEXT NOT NULL,
  codigo_interno TEXT UNIQUE NOT NULL,
  area_id INTEGER,
  email TEXT UNIQUE,
  telefono TEXT,
  fecha_ingreso DATE,
  rol_organizacional TEXT NOT NULL,
  estado_laboral TEXT DEFAULT 'Activo',
  ausencia_desde DATE,
  ausencia_hasta DATE,
  tipo_ausencia TEXT,
  motivo_ausencia TEXT,
  created_by INTEGER,
  updated_by INTEGER,
  motivo_cambio TEXT,
  created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
  updated_at DATETIME DEFAULT CURRENT_TIMESTAMP
);

User Account Entity

Authentication and authorization data stored in the usuarios table:

CREATE TABLE usuarios (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  persona_id INTEGER UNIQUE NOT NULL,
  username TEXT UNIQUE NOT NULL,
  password_hash TEXT NOT NULL,
  rol_id INTEGER,
  estado_usuario TEXT DEFAULT 'Activo',
  must_change_password INTEGER DEFAULT 1,
  created_by INTEGER,
  updated_by INTEGER,
  motivo_cambio TEXT,
  created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
  updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
  FOREIGN KEY (persona_id) REFERENCES personas(id),
  FOREIGN KEY (rol_id) REFERENCES roles(id)
);

Operational Assignment Entity

Stored in asignaciones_operativas table:

CREATE TABLE asignaciones_operativas (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  persona_id INTEGER NOT NULL,
  proceso_id INTEGER NOT NULL,
  maquina_id INTEGER,
  turno TEXT NOT NULL,
  permanente INTEGER DEFAULT 0,
  fecha_inicio DATETIME DEFAULT CURRENT_TIMESTAMP,
  fecha_fin DATETIME,
  created_by INTEGER,
  created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
  FOREIGN KEY (persona_id) REFERENCES personas(id),
  FOREIGN KEY (maquina_id) REFERENCES MAQUINAS(id)
);

Best Practices

State Management

Always check estado_efectivo: When displaying personnel status, use estado_efectivo rather than estado_laboral to account for expired absences
Respect terminal states: The Baja status is terminal and immutable. Design your UI to prevent modification attempts
Validate absence data: When changing to non-Activo states, ensure all required absence fields are provided

Security

Permission enforcement: All endpoints enforce role-based access control. Ensure your client application handles 403 Forbidden responses
Password handling: Never log or store temporary passwords. Send them via secure channels only
Audit trail compliance: Always provide meaningful motivo_cambio values for audit compliance

Performance

Use GET /catalogos once: Cache the areas and roles catalogs in your client application rather than fetching on every form render
Batch operations: When updating multiple personnel records, make parallel requests to improve throughput
Detail endpoint for full data: Use GET /:id only when you need complete historical data. Use GET / for listing views

Error Handling

try {
  const response = await fetch('/api/personal', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify(personnelData)
  });
  
  const result = await response.json();
  
  if (!result.success) {
    // Handle business logic errors
    alert(result.error);
  } else {
    console.log('Personnel created:', result.data);
  }
} catch (error) {
  // Handle network or server errors
  console.error('Request failed:', error);
}

Authentication

Production

Quality Control

Resources

Personnel & Groups

Dashboard & Analytics

Operations

System

​Personnel Management API

​Permissions

​Get All Staff

​Authorization

​Response Schema

​Business Logic

​Get Staff Details

​Parameters

​Authorization

​Response Schema

​Register Staff

​Authorization

​Request Body

​Response Schema

​Business Logic

​Error Responses

​Update Staff

​Parameters

​Authorization

​Request Body (All fields optional)

​Business Logic

​Terminal State Protection

​Estado Laboral Rules

​Audit Trail

​Error Responses

​Assign Role

​Parameters

​Authorization

​Request Body

​Business Logic

​Error Responses

​Reset Password

​Parameters

​Authorization

​Response Schema

​Business Logic

​Assign Operation

​Parameters

​Authorization

​Request Body

​Business Logic

​Assignment Validation

​Error Responses

​Toggle Access

​Parameters

​Authorization

​Request Body

​Business Logic

​Error Responses

​Get Catalogs

​Authorization

​Response Schema

​Usage

​Get Operational Roles

​Authorization

​Response Schema

​Operational Roles vs System Roles

​Data Models

​Personnel Entity

​User Account Entity

​Operational Assignment Entity

​Best Practices

​State Management

​Security

​Performance

​Error Handling

Build docs developers (and LLMs) love

Personnel Management API

Permissions

Get All Staff

Authorization

Response Schema

Business Logic

Get Staff Details

Parameters

Authorization

Response Schema

Register Staff

Authorization

Request Body

Response Schema

Business Logic

Error Responses

Update Staff

Parameters

Authorization

Request Body (All fields optional)

Business Logic

Terminal State Protection

Estado Laboral Rules

Audit Trail

Error Responses

Assign Role

Parameters

Authorization

Request Body

Business Logic

Error Responses

Reset Password

Parameters

Authorization

Response Schema

Business Logic

Assign Operation

Parameters

Authorization

Request Body

Business Logic

Assignment Validation

Error Responses

Toggle Access

Parameters

Authorization

Request Body

Business Logic

Error Responses

Get Catalogs

Authorization

Response Schema

Usage

Get Operational Roles

Authorization

Response Schema

Operational Roles vs System Roles

Data Models

Personnel Entity

User Account Entity

Operational Assignment Entity

Best Practices

State Management

Security

Performance

Error Handling