GitHub - finkedave/django-staff: In the Django Authentication package is that all users use the same model/profile. This can be a drawback if you have lots of users or you want different information stored for your staff members, such as bio, contact info, etc. It is also handy for linking to models for author fields so the lookup is quicker.

finkedave / django-staff Public

forked from callowayproject/django-staff

Notifications You must be signed in to change notification settings
Fork 0
Star 1

In the Django Authentication package is that all users use the same model/profile. This can be a drawback if you have lots of users or you want different information stored for your staff members, such as bio, contact info, etc. It is also handy for linking to models for author fields so the lookup is quicker.

Apache-2.0 license

1 star 2 forks Branches Tags Activity

Star

Notifications

Branches Tags

Name		Name	Last commit message	Last commit date
Latest commit History 90 Commits
data		data
doc_src		doc_src
docs		docs
example		example
staff		staff
.gitignore		.gitignore
LICENSE.txt		LICENSE.txt
MANIFEST.in		MANIFEST.in
README		README
TODO.txt		TODO.txt
build_docs.sh		build_docs.sh
setup.py		setup.py

Repository files navigation

============
Django Staff
============


In the Django Authentication package all users use the same model/profile. This can be a drawback if you have lots of users and you want different information stored for your staff members, such as bio, contact info, etc. It is also handy for linking to models for author fields so the lookup is quicker.

The staff models are automatically created and managed by the ``is_staff`` property of ``Users``. The staff profile is automatically added to the ``User`` admin screen.