Hi John,
I don't know if this would work for you as you indeed have an extra level.
I'll do it this way
Authorities are the permissions from Django, for example you may have
custom permissions (authorities in your case): "can_add_employee",
"can_edit_employee", "can_view_employee"
Roles would
Hi all,
I agree that it's perfectly fine to not use the built in auth and admin
apps, and people do it all the time. But, I wanted to give a quick proof of
concept of using the admin with custom permissions.
# models.py
from django.contrib.auth.models import AbstractBaseUser
from django.db
Gabriel,
How would you store groups for each company within the default "groups"
database? Our current database design is
Company
CustomUser belongs to Company
Roles belongs to Company (replacing default "Groups" with "Roles")
Roles has many Authorities (replacing default "Permissions" with
Hello!
I would suggest to not drop the use of the built in auth module. You have
many template and view tags, decorators, etc which are very helpful.
You may, for example create a group for each company/branch then add each
user to their respective groups upon registration.
Each groups may
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
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
Hi Carl,
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)?
We will create our own authorization module for permissions/roles and
groups.
Best,
John
On Friday, November
Hi John,
I'll start with answering the question in your subject: no. There's
nothing at all wrong with using the parts of Django that are useful to
you, and not using the ones that aren't.
In particular, auth and admin are part of "contrib"; that is, useful
applications built on top of Django
We are evaluating django for a new internal CRM project and have issues
using many of the built in features including: the base user, permissions,
and authentication.
We do not wish to use the built-in admin... The level of complexity for
our permissions will be based on the employees job
9 matches
Mail list logo
