On Fri, Feb 6, 2009 at 5:48 AM, mguthrie <mitchguth...@gmail.com> wrote:
> > Anybody? > > On Feb 3, 9:41 am, mguthrie <mitchguth...@gmail.com> wrote: > > I'm looking at creating an application that would use Django Auth for > > managing users but once logged in the user will "belong" only to a > > specific organization and can only work with data associated with that > > organization. I've looked at using the Django Sites contrib but I > > would like something that is dynamically assigned and not specified in > > the settings file like sites. > > > > What would be the best route to adding this functionality? From what > > I've looked at so far it might be best to create a Manager that would > > handle the model end of things and filter based off of the > > organization id. > > > > Any ideas would be welcome. Also, is there a better way to do this > > that wouldn't require having a separate DB for each organization? I > > would like each account to be assigned to an organization unless it's > > a superuser account which would be able to oversee the entire > > application. > > > > Thanks in advance. > > > This is interesting. In the few minutes I spent thinking about it, I couldn't come up with a very compelling solution, but maybe user profiles[1] are what you are looking for. -- Best, R [1] - http://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. 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 -~----------~----~----~----~------~----~------~--~---
