When you're talking about a table of Users you are talking about an entity of User. This can contain extra stuff that's not relevant to the frontend - like the password or lastUpdatedDate, you name it.
In your example, when you talk about a Model, you talk about a user Entity representation. There's a transformation there. The frontend posts a Model (or a DTO) to the backend API, the backend does the transformations it needs (e.g. retrieving the user Entity based on the model user id, mapping updated field values from the model to the Entity, and saving the Entity to the database).
The view is the representation template, the model is what's needed to fill in the template, and the controller does CRUD operations to a backend API.
Edit: or is this MVVM? These days I mainly do backend stuff but I used to call this MVC
When you're talking about a table of Users you are talking about an entity of User. This can contain extra stuff that's not relevant to the frontend - like the password or lastUpdatedDate, you name it.
In your example, when you talk about a Model, you talk about a user Entity representation. There's a transformation there. The frontend posts a Model (or a DTO) to the backend API, the backend does the transformations it needs (e.g. retrieving the user Entity based on the model user id, mapping updated field values from the model to the Entity, and saving the Entity to the database).
The view is the representation template, the model is what's needed to fill in the template, and the controller does CRUD operations to a backend API.
Edit: or is this MVVM? These days I mainly do backend stuff but I used to call this MVC