Yeah you can use ViewModels.
These are regular classes that contain properties that you need for your view. And these properties could be a subset of a model or the combination of multiple models.
For the login view you could create a LoginViewModel
public class LoginViewModel
{
public int UserId {get; set;}
[Required]
public string Username {get; set;} //included required attribute for username
public string Password {get; set;}
}
You can now project your viewmodel from your database query (or any other source).
ViewModels are very helpful as in many cases the views typically don't map one to one with models or may be need annotations that you are not willing to add to your models directly.
So many great uses.