Need advice on writing very specific custom user roles

[Ahmad Zoughbi]

Hello,

I need to build custom Django user roles, and i need an advice on the best approach (or library that i can use) to achieve that:

1. There will be 3 different user levels:

1. Author

2. Editor

3. Verification

2. Every user must be limited to a city, based on custom field (New York, Berlin, Amsterdam, etc)

3. Only ‘Author’ can add content, while ‘Editor’ and ‘Verification’ can edit the content.

4. Author: Can only view/edit the content created by them.

5. Editor: Can only view/edit the content created by ‘Author’s in their cities.

6. Verification: Can only view/edit the content created by the ‘Editor’s in their cities.

7. Author: When creates content, should have the options to:

1. Save as draft

2. Send to Editor

8. Editor: When edits content, should have the options to:

1. Send back to Author

2. Send to Verification

9. Verification: When edits content, should have the options to:

1. Send back to the Editor

2. Mark as Verified.

Scenario:

An admin creates the following users:

Username | Role | City | Content titles written by the user

John | Author | New York | Test1, Test2, Test3

Sam | Author | New York | Test4, Test5, Test6

Kim | Author | Berlin | Test7, Test8, Test9

Adam | Editor | New York

Alex | Editor | Berlin

Stacey | Verification | New York

Anthony | Verification | Berlin

Based on the above scenario, the Authors below should be able to access only the titles they created; Additionally:

Adam: Should be able to view/edit the titles: Test1 - Test6 (Since they were written by 2 Authors in his City.

Alex: Should be able to view/edit the titles: Test7 - Test9 (Since they were written by Kim, which in his city)

The same applies for the Verification.

Finally, If Author sent the content to Editor, the Author should no longer be able to edit the content, until it’s sent back to him by the Editor.

[Melvyn Sopacua]

It requires some work writing the permissions, but this is what
django-guardian [1] is good at. I would ditch Role as a user attribute
and use groups instead. If cities are limited in number, I would make
city groups as well and then it's just a matter of filtering groups
the right way taking article state into account.

[1] https://djangopackages.org/packages/p/django-guardian/

> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users...@googlegroups.com.
> To post to this group, send email to django...@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/46db433a-a6c5-4e6b-92f0-e605b8e7b2f0%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Melvyn Sopacua