ASP.Net MVC should you create a model for each view?

I'm fairly new to ASP.Net MVC and I find myself making a single model class for every view. E.g. SignInModel, SignUpModel, EditProfileModel and so forth.

Many of these are somewhat similar, having the same DB fiels, and then a few custom properties.

Is this really how MVC is supposed to be done, or did I miss some aspect of it ?

I realize this may be subjective, but there ought to be a "best-practice" around this.