User Permissions #693
Open
User Permissions #693
+359
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for ami-dev canceled.
|
|
|
This looks really promising, great work @mohamedelabbas1996. I will review asap! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request implements a fine-grained object-level permissions for the Project model using
django-guardian. It ensures that only staff users can create projects, while project owners are granted read, write, and delete permissions. Project members have read and write permissions, and other users are restricted to only read permissions. Additionally, user permissions are included in the API response for every project object. Finally, the project’s object-level permissions can be managed through the Django admin page.