User data model
Each user account contains three fields:UsuarioItem.cs
| Field | Description | Example |
|---|---|---|
ID | Unique numeric identifier for the user. Assigned at creation and read-only after saving. | 001 |
NombreUsuario | The username used to log in. Must be unique across all accounts. | Luis_Admin |
Password | The account password stored for authentication. | — |
CRUD workflow
Adding a user
Open the Usuarios screen
Navigate to the Administration section and select Usuarios from the sidebar.
Editing a user
Select a user
Click on the row in the table that corresponds to the account you want to update. A row must be selected before you can edit.
Click Editar
Click Editar. The AgregarUsuarioWindow dialog opens in edit mode, pre-populated with the selected user’s current values.
Update the fields
Change the NombreUsuario or Password as needed. The ID field identifies the record and should not be changed.
If you click Editar without first selecting a row, the application displays the message: “Por favor, selecciona un usuario de la tabla para editar.” Select a row and try again.
Deleting a user
Click Eliminar
Click Eliminar. A confirmation dialog appears:
¿Estás seguro de que deseas eliminar al usuario ?The dialog uses a Yes/No warning prompt (per requirement RF_3.16).
Sample accounts
The following accounts are pre-loaded as sample data:| ID | NombreUsuario | Notes |
|---|---|---|
001 | Luis_Admin | Administrator account |
002 | Ariel_Lara | Standard user |
003 | User_Test | Test account |
Best practices for usernames
Use a consistent format
Adopt a naming convention and apply it uniformly. For example,
Firstname_Lastname or Role_Name (as seen in Luis_Admin and Ariel_Lara). Consistency makes it easier to identify account owners at a glance.Avoid special characters
Stick to letters, numbers, and underscores in usernames. Special characters or spaces can cause unexpected behavior in downstream systems that consume the username field.
Reflect roles in admin usernames
For accounts with elevated privileges, include a role indicator in the username (e.g.,
_Admin). This makes it visually clear in the table which accounts have administrative access.Disable test accounts before go-live
Delete or rename accounts created for testing purposes before the application goes live. Test credentials with known passwords are a common security risk.