# Product states

States communicate where an operation or user stands.

## General guidelines

1. States are written in lowercase with an uppercase initial.
   ✅ "En progreso" / "Sin comenzar" / "Finalizado" / ❌ "EN PROGRESO" / "en progreso"

2. Before choosing a term, consider: type of operation and flow, user profile (admin or collaborator), and whether an existing term can be reused.

3. You can use the same pill color for similar states. A different pill per state is not required.

## Operation states

### Initial / zero states

**Borrador**
- The operation is not ready to be executed or published.
- The creator can edit everything without restrictions.
- Sends no notifications and is invisible to collaborators.
- Examples: evaluation cycle not yet configured, form not completed.

**Sin comenzar**
- The operation is published and available, but no one acted on it yet.
- The process has started for the system, but not for the user.
- It is not editable (unlike Borrador).
- Examples: available survey the collaborator hasn't answered, evaluation not started.

> Key difference: Borrador = the admin/creator still owns it. Sin comenzar = the participant hasn't acted yet.

**Inactivo/a**
- Something exists but is not enabled, not in use, has no effect.
- A structural state, not a progress state.
- Applies to objects or configurations, not personal tasks.
- Examples: disabled module, assignment rule turned off.

> Activo ↔ Inactivo indicate whether something is enabled, not whether it has started or finished.

**Sin asignar**
- No designated person to execute, review, or handle the operation.
- The process cannot advance until someone is assigned.
- Examples: ticket without agent, evaluation without an evaluator.

### Intermediate states

**En proceso**
- The operation has started and actions are being taken, but it is not done.
- For non-instant operations with multiple stages: requests, tickets, approval flows.
- Requires several actions before completion.

**En progreso**
- Similar to "En proceso" but with a more dynamic tone, oriented to ongoing activity.
- For: evaluations, surveys, training.
- There is already evidence of progress.

**Pendiente**
- A requirement or decision is missing before the operation can advance.
- Communicates active waiting, not lack of start.
- The next action depends on a person, not the system.
- Examples: request pending approval, stage waiting for confirmation.

**Pausado/a**
- A process that was underway is temporarily and reversibly stopped.
- There was prior progress, but it has been frozen.
- A pause is not an error: it is controlled waiting.
- Example: a survey whose activity is temporarily suspended.

**Asignado/a**
- A responsible person has been designated, but hasn't started yet.
- It is the step between "Sin asignar" and "En progreso".
- Examples: evaluator assigned who hasn't evaluated yet, agent assigned to an unopened ticket.

| State | What it indicates |
|---|---|
| Sin asignar | No one is responsible yet |
| Asignado/a | Responsible assigned, hasn't started |
| En progreso | Responsible has started |

### Final states

**Activo/a**
- An operation, module, rule, or cycle is enabled, available, and in operation.
- It is the direct opposite of "Inactivo".
- Examples: published survey that collaborators can answer.

**Completado/a**
- All required actions were performed by the user.
- The main action was taken by the user (not the system). Nothing pending.
- Tone of individual fulfillment: "I finished it".
- Examples: collaborator who finished a survey, evaluator who finished an evaluation.

**Cerrado/a**
- A process is administratively concluded.
- No more actions, modifications, or participation accepted.
- Closing depends on the system or the admin, not on the user.
- Examples: resolved ticket, request that finished its flow, applications period closed.

**Finalizado/a**
- A process reaches its natural end: all stages were completed.
- No pending actions remain for anyone.
- Neutral and formal tone, unlike the administrative closure of "Cerrado".
- Examples: evaluation cycle that finished all its stages, survey completed by everyone.

## User states

### Admin panel — Platform

| State | Color | Definition |
|---|---|---|
| Sin ingresar | Yellow | Invited user who hasn't entered the community yet. |
| Activado | Green | User who has logged in at least once. |
| Desactivado | Gray | Removed user. Their data is kept and is billable to the organization. |

### Admin panel — Time Tracking module

| State | Color | Definition |
|---|---|---|
| Activo | Green | Working. Clocked in and timer running. |
| Inactivo | Yellow | Clocked in but timer paused. |
| (no label) | Gray | Not clocked in. |

### Community / app — Chats module

| State | Definition |
|---|---|
| Usuario deshabilitado | Groups users deactivated and removed by an Admin. Deliberately disabled; cannot access or interact. |

> "Deshabilitado" was chosen because it implies the user was deliberately disabled — unlike "desactivado", which has a different meaning in the Admin panel.
