# Controllers or Actions

**URL:** <https://www.ruby-forum.com/t/controllers-or-actions/120031>\
**Category:** Rails\
**Created:** [November 13, 2007, 6:25am UTC](https://www.ruby-forum.com/t/controllers-or-actions/120031 "2007-11-13T06:25:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mojave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@Mojave](https://www.ruby-forum.com/u/Mojave)\
**Post date:** [November 13, 2007, 6:25am UTC](https://www.ruby-forum.com/t/controllers-or-actions/120031/1 "2007-11-13T06:25:09Z")

</div>

I’m fairly new to Rails and I’m developing a site with the usual  
register/login/logout/forgotpassword functionality.

I know everyone has their own way of doing things, but I was wondering  
if there is a preferred standard for designing the controllers/actions  
for this functionality. Would all of those be grouped into one  
controller with specific actions or would each of them get their own  
controller?

---

<div class="post-metadata">

**Author:** ![Mojave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@Mojave](https://www.ruby-forum.com/u/Mojave)\
**Post date:** [November 13, 2007, 10:51am UTC](https://www.ruby-forum.com/t/controllers-or-actions/120031/2 "2007-11-13T10:51:50Z")

</div>

i don’t know if there’s a standard for doing it, but i normaly would do  
it like this:  
one controller (UsersController) for registering a new user, allow him  
to edit or delete his account data and the forgotten password  
functionality  
another one (SessionsController) for login/logout (create/destroy  
session)

that way you can keep the thing mostly restful