I’m not looking for a complete solution, maybe just a nudge in the right
direction? For example, rather than restricting users to
updating/creating certain classes
(which seems to be the most common example give for
Authorisation/authentication gems) how do I restrict a certain
user to a single instance of a class and the multiple other classes that
belong to it?
Say, for example I have a site for many authenticated/authorised Users:
These users are employed at different Companies, many of which might
Users employed at one company will never access details of another
company or even be aware of their existence.
I was wondering if nested resources or using the database structure was
way to go but I read that more than 2 nesting depths was very bad for
Are there any gems/open source projects that make it simpler to
this setup: eg: a single point of entry (on login page for any user) but
then redirect them automatically to the Project list in the
Company/Office they belong to?
Thanks in advance for any advice you can give.