From 18669ec1fb72f09953c9d5d94b7ebd16c17fcf85 Mon Sep 17 00:00:00 2001 From: benzkji Date: Fri, 27 Oct 2017 18:31:15 +0200 Subject: [PATCH] docs --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7dc60a6..452a3c6 100644 --- a/README.md +++ b/README.md @@ -1,15 +1,19 @@ # django-separate-users -separate staff and non staff users with two proxy models (FrontendUser and Editor). + +Separate staff and non staff users with two proxy models (FrontendUser and Editor). Nothing fancy, but as I ended up doing this again and again, this is a simple plug and forget solution, that I'll probably use in many projects from now on. +- minimal requirement are the `is_staff` and `is_superuser` fields on your user model - staff users can be given the right to edit non staff users (currently not possible, or everyone can make everyone a superuser) - fieldsets for staff and non staff users can be defined via settings (not yet) - better admin list views (filters, is_active, etc) -NOTE / WARNING: With django<1.11, it's not possible to run this app with as custom +[//]: # (NOTE / WARNING: With django<1.11, it's not possible to run this app with as custom `settings.AUTH_USER_MODEL`. See https://stackoverflow.com/questions/46935758/djangos-get-user-model-only-in-1-11-during-import-time +t) +NOTE: Custom user models are not supported (yet). ## Usage