Well, django user auth has groups implemented. "It handles user accounts, groups, permissions and cookie-based user sessions." (http://docs.djangoproject.com/en/dev/topics/auth/? from=olddocs)
How can you effectively separate their views. Separate your apps based on their nature, not based on who is going to be using them. Once you do that, you can lock down all of your views trivially. Now, one thing, i did'nt understand your problem in great details, BUT, it seems to me that you just want to inherit the User class and add a bunch of fields to it to get what you want done. On Oct 21, 2:39 pm, itsnotvalid <[EMAIL PROTECTED]> wrote: > I am going to help some people making a website that has a few admins, > a crowd of service providers (individuals) and customers. There could > be agents who invites people to become service providers or customers > as well. > > Looking at the user system provided by django, and as a new programmer > to django, I am not sure how can I separate different kinds of user > here. I actually want to make it look like that different people login > in different location, and do not share the same view after they > logged in. > > So I am thinking a model schema like this: > > Users (as usual) > > Providers(link to a specific user, one-to-one) > > Customers(link to a specific user, many-to-one, as one user may find > services for more that one actual person) > > Agents(link to a specific user, one-to-one) > > But how effectively can I separate their views? By defining different > apps? Any other suggestions? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
