MVC: Do I need a separate controllers for Users and Archived Users

Intro: I'm fairly new to Laravel and MVC.

I am in a process of making all the front-end of the system, which setting up the controller and view files.

Now the system will have users, so I created UsersController for its CRUD, but instead of delete, the users can be archived and un-archive.

Archived users cannot logged in anymore, they will be separated from the database table where the active users are, they can also be un-archive incase they got employed in the future.

How should I tackle this? Any tips?

from Newest questions tagged laravel-5 - Stack Overflow http://ift.tt/2rbk1tm
via IFTTT