Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Esteban-Mendez-j/Proyecto-Docker/llms.txt

Use this file to discover all available pages before exploring further.

Platform administrators have elevated access across all of SearchJobs. As an admin, you can view every registered user and every vacancy on the platform, change the active state of user accounts, disable or re-enable vacancies, manage admin role assignments, and review data analytics. Admin access is assigned at the system level—users do not self-register as admins.

​
What admins can do

User management

List all users (candidates and companies), view their details, and ban or unban accounts with a comment.

Vacancy management

List all vacancies platform-wide, toggle active status with a comment, and filter by any criteria.

Role management

Grant or revoke the admin role for any user account.

Analytics dashboard

View an embedded Power BI dashboard with platform-wide data analysis.

​
Admin access

The admin role is assigned at the system level using the admin API. A user with an existing account can be promoted to admin, or an admin role can be removed, without any action required from the affected user. The admin panel is accessible only to authenticated users who hold the admin role. Admins see navigation options and pages that are not available to regular candidates or companies.
Admins authenticate with the same login flow as candidates and companies. The difference in access is determined by the role assigned to the account.

​
Analytics dashboard

Navigate to the Panel de Administrador (Admin Index page) to view the platform analytics. The main content area embeds a Power BI report titled DataSet SearchJobs that provides a full breakdown of platform activity and data.

​
User management

Navigate to Admin Usuarios to manage all registered users on the platform. The UsuariosActivos component lists every user account. You can filter the list using the following criteria available through the admin API:
  • Name — filter by the user’s name.
  • Email — filter by email address.
  • Role — filter by principal role (candidate or company).
  • Status — filter by active or inactive account state.

​
Banning a user

1

Find the user

Locate the user in the list. Use the available filters to search by name, email, or role.
2

Initiate the ban

Click the ban action for the user. A confirmation modal appears asking you to confirm the action for the selected user.
3

Confirm

Click Confirmar in the modal. The system calls the POST /api/admin/cambiar-estado/usuario endpoint, which:
  • Sets the user’s isActive flag to false
  • Records your comment against the user’s account
  • Automatically updates all of the user’s associated postulations to reflect the inactive state

​
Unbanning a user

The unban flow mirrors the ban flow. Locate the user, initiate the unban action, and confirm. The system sets the user’s isActive flag back to true and updates associated postulations accordingly.
If you attempt to change a user’s status to the state they are already in, the API returns an error: “El usuario ya se encuentra en ese estado” (the user is already in that state). No change is made.

​
Vacancy management

Navigate to Admin Vacantes to manage all vacancies across the platform. The VacantesActivas component lists all platform vacancies. You can filter vacancies using the same filter criteria available to companies, plus the following admin-only filters available through the admin API:
  • Active state — filter by active, inactive, paused by company, or all vacancies.
  • All standard vacancy filters — title, modality, salary, experience, and more.

​
Disabling a vacancy

1

Find the vacancy

Locate the vacancy in the admin vacancies list.
2

Toggle the active state

Use the disable action for the vacancy. Provide a comment explaining the reason for disabling it.
3

Confirm

The system calls POST /api/admin/cambiar-estado/vacantes, which:
  • Sets the vacancy’s active flag to false
  • Records your comment against the vacancy
  • Automatically updates all postulations associated with that vacancy
Disabled vacancies appear with the status Desactivadas por admin in the job board and are not visible to candidates. Companies can see them in their own vacancy list with this status. To re-enable a vacancy, use the same flow with estado=true.
As with users, if you attempt to change a vacancy to the state it is already in, the API returns an error: “La vacante ya está [estado]”. No change is made.

​
Role management

Admin roles can be granted or revoked through the admin API:
  • Grant admin — calls POST /api/admin/agregarRol with idUsuario and estado=true, assigning the admin role to the specified user.
  • Revoke admin — calls POST /api/admin/removerRol or POST /api/admin/agregarRol with estado=false, removing the admin role from the specified user.

​
Platform oversight and appeals

Admins have full visibility into all appeals submitted by candidates. The appeals system (/api/apelacion) allows you to:
  • List all appeals via GET /api/apelacion/admin/list — returns every appeal registered in the system.
  • Change the status of an appeal via POST /api/apelacion/cambiarEstado/{idApelacion} — pass the new status to update an appeal after reviewing it.
  • Delete an appeal via DELETE /api/apelacion/delete/{id} — permanently removes an appeal record.
Use the appeals list to identify candidates who dispute rejection decisions and resolve disputes by updating the appeal status after your review.

Build docs developers (and LLMs) love

Get started for freeTalk to us