If you use the above method, you do not need to use a with_scope on UserSession.

By placing ‘authenticates_many :user_sessions’ in the Account model, Authlogic creates an association between the Account and the UserSession and some other magic behind the scenes/.

So now you can call ‘@current_account.user_sessions.build’ to scope it to the account.

I assume if you want to call ‘UserSession.build’ and have it automatically scope to account, then you would need with_scope, but are there any benefits of not going through the account/usersession relationship?

I’m still a little confused about what you should use to find the current session though? In the Authlogic docs it seems that you’re meant to do a with_scope find, like this (in ApplicationController to find current_session):

UserSession.with_scope(:find_options => {:conditions => “account_id = #{current_account.id}”}, :id => “account_#{current_account.id}”) do
UserSession.find
end

But when I try and implement this I don’t seem to be able to login. Or rather, the login validates but then I’m sent straight back to the login.

Do we even need to use the above or am I getting confused with something?!

Refer to: http://rdoc.info/rdoc/binarylogic/authlogic/blob/f2e95179acf87f11b44c7a58e6083cf84cddff27/Authlogic/Session/Scopes/ClassMethods.html

So this means we have one model, and two controllers: a normal scaffolded user (not mentioned above) and the admin bits you describe above?