> > Complicated indeed! > I once worked on a similar project that tackled the first 2 requirements as part of a multi-tenant application, storing both the userID and company ID for each detail record (content). Plus, the user profile was extended to tie a User record to one or more companies.
For your third requirement, sharing between companies, I would imagine a many-to-many relationship on a per record basis that recorded any sharing that was setup. All of this permission stuff would have to be checked in your views - a mixin would be appropriate with class-based views. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/bBUBWd7lEGMJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
