Perfect. That answers my question. I was trying to avoid having the two tables in the db -- but we will just disregard them.
Thank you for all of the input and quick replies. Django appears to have a great community and we are excited to get started. On Friday, November 21, 2014 3:42:46 PM UTC-6, Carl Meyer wrote: > > Hi John, > > On 11/21/2014 02:33 PM, John Rodkey wrote: > > Thank you for the quick answer. Using your recommendation, can we > simply > > disable the admin, groups and permissions, but still use the > Authentication > > (login/sessions)? > > The admin is already separate from auth, so that's easy to turn off. > > With the built-in groups and permissions, you will still have tables for > them in the database, but they don't need to be linked to your custom > User class (as I described in my last mail), so you can basically just > ignore them and use your own authorization module instead. > > Carl > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3bcba735-fa87-477c-8c33-1c7b99718efc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
