My question concerns the convention for using two different Controllers to influence the same Model.

I have a catalogue section of this website, and generally speaking, it's controlled by, appropriately enough, the Catalogue Controller. However, I'm also coding the Administrative functionality of adding, editing, or removing entries in the catalogue. Generally speaking, Admin functionality is being handled by the Admin Controller.

If I'm trying to give admins the ability to edit the catalogue, would the proper or accepted convention be to add that functionality to the Catalogue controller, or to the Admin controller? Is it even advisable to have a separate Admin controller? Obviously both methods would work, and there may not even BE an accepted convention, but I wanted to check.