While he may have misunderstood, in principle the approach will be similar.
You'll have a tenant model that each user belongs_to and all items created will be assigned to the tenant of the acting user, likely with an before_create callback. Probably would be good to pull that out into a module. See the cookbook source, app/models/owned_model.rb for a good example of how you can get associations and permissions separated out. Not demonstrated there but you can also define fields and lifecycles within classy modules. -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/hobousers/-/aVsZqUtwW5wJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
