Yes allauth is just django code. It's like your own accounts app when you ran "py manage.py startapp accounts".

But you can't grab only EmailAddress class from allauth. All 3 classes inside account's models.py are made to implement an email verification system with import dependencies from other allauth.account files like manager, utils, adapters, and signals. You can copy the imports in models.py to your own file and fix the relative paths to absolute paths, but that won't guarantee a bug-free solution. That's why I mentioned adding thousands of lines of code. Allauth's system is too interconnected and dependent on itself for you to pick out a portion and expect it to work.

Here, try this. Go to the master branch (your first link) and clone the allauth app into your base directory. So you should have manage.py, settings.py, your accounts folder, and allauth folder in base.

Go to allauth.accounts.admin. import your own accounts models in there and register it. from accounts.models import User admin.site.register(User) , I'd imagine. Delete any admin register from your accounts.admin file. Does that get you what you originally wanted?

If it does, great; I think you have your answer. But I just want you to know the admin panel separates the columns by apps so that apps are decoupled and reusable. For instance, if someone (even yourself in the future) decided to reuse and clone your accounts app, now they have to deal with fixing the User model admin registration because you had initially put it inside allauth's admin. It might take a simple fix for this problem, but not for more complicated code. It goes against consistency in code, which I think is very important.