On 15 December 2016 at 03:43, Avraham Serour wrote:
> Hi,
>
> I've given a lot of thought on this, I have also searched for django apps
> that deal with permissions, I didn't find something that implements
> hierarchical object level permissions, I have a feeling that I am
> overcomplicating thing
Hi,
I've given a lot of thought on this, I have also searched for django apps
that deal with permissions, I didn't find something that implements
hierarchical object level permissions, I have a feeling that I am
overcomplicating things if none did this...
Well, first of all I thought of creating
Yes, mptt can save your day.
When handling hierarchies it's important to establish clear priorities.
An example: given the following hierarchy: Project (1st "floor") -> Module
(2nd "floor") -> Task (3rd "floor"), if not directly assigned, a task
should consider module's permission? Or the project
Hi,
Thanks for taking your time on this.
> Could a child object have a different permission from its parent?
Yes, I'm thinking someone may have access to the parent but not to all
childs, or read access to the project and write access to some tasks
(probably the ones I'm responsible)
So each obje
Considerations follow inline...
On 11 December 2016 at 03:34, Avraham Serour wrote:
> ...
>
> So should I check the parent object permissions? or just checking the
> current object is enough?
It depends on the granularity level of your permissions.
Could a child object have a different permissi
Hi,
I'm using DRF and need to implement object based permissions, I
sublassed BasePermission to create my own logic.
Currently all models that make sense to have permission inherits from a
base Object model, implementing common behaviour and fields.
The object has two many to many fields to User
6 matches
Mail list logo
