Hi Adam,
Thanks for the feedback!
I tried to leverage app auth framework to customize User, Permission, Group, PermissionMixin models.
As for the User it works normally. There is the possibility to extend the models and place the db_table in the User Meta. There is also a constant AUTH_USER_MODEL to identify the CustomUser model that will be used for authentication. There are also the constant USERNAME_FIELD, EMAIL_FIELD to identify the model fields.
The documentation also contains guidance on the AUTHENTICATION_BACKENDS constant to customize the authentication rules.
I suggest the possibility of thinking about having similar constants for the Permission, Group, PermissionMixin models for a next update.
For example, for the Pemisson model we can access it alternatively through an identification of a constant AUTH_PERMISSION_MODEL. The rest likewise AUTH_GROUP_MODEL, AUTH_USER_PERMISSIONS_MODEL, AUTH_USER_GROUPS_MODEL, AUTH_GROUP_PERMISSION_MODEL.
It could also have the possibility of constants to identify the name of the fields in each of these models of the Auth app. For Permission would have: NAME, CODENAME. For Group it would have: NAME.
Respectfully,
Jansen