Allows you set essentially set up a relationship with your sessions. See module definition above for more details.

Options

• session_class: default: "#{name}Session", This is the related session class.
• relationship_name: default: options[:session_class].klass_name.underscore.pluralize, This is the name of the relationship you want to use to scope everything. For example an Account has many Users. There should be a relationship called :users that you defined with a has_many. The reason we use the relationship is so you don‘t have to repeat yourself. The relationship could have all kinds of custom options. So instead of repeating yourself we essentially use the scope that the relationship creates.
• find_options: default: nil, By default the find options are created from the relationship you specify with :relationship_name. But if you want to override this and manually specify find_options you can do it here. Specify options just as you would in ActiveRecord::Base.find.
• scope_cookies: default: false By the nature of cookies they scope themselves if you are using subdomains to access accounts. If you aren‘t using subdomains you need to have separate cookies for each account, assuming a user is logging into more than one account. Authlogic can take care of this for you by prefixing the name of the cookie and session with the model id. Because it affects both cookies names and session keys, the name `scope_cookies` is misleading. Perhaps simply `scope` or `scoped` would have been better.