-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permissions #912
Milestone
Comments
KasperBrandt
added a commit
that referenced
this issue
Nov 25, 2014
A new object level permissions system is now in place, which contains: - A rule based system (rules defined in permissions.py) - Auth.group is now linked to rsr.Employment - A new field on User level, 'is_admin', for general RSR admins aka Akvo employees - Four new Groups: Admins, User managers, Project editors and Users - The admin corresponds to the permissions, showing only the models and objects that a user can add or edit
KasperBrandt
added a commit
that referenced
this issue
Nov 25, 2014
Changed the MyRSR page so that a user can select a Group for every Employment (but only if allowed). The API now also checks if a user is allowed to change that particular employment.
KasperBrandt
added a commit
that referenced
this issue
Nov 25, 2014
KasperBrandt
added a commit
that referenced
this issue
Nov 25, 2014
Updated the REST API to work with object level permissions. Also made updates to MyRSR to set any Group, updated signals.py for updating users when their Employment is adjusted or created and cleaned up old permissions.
KasperBrandt
added a commit
that referenced
this issue
Nov 25, 2014
KasperBrandt
added a commit
that referenced
this issue
Nov 25, 2014
KasperBrandt
added a commit
that referenced
this issue
Nov 25, 2014
KasperBrandt
added a commit
that referenced
this issue
Nov 26, 2014
KasperBrandt
added a commit
that referenced
this issue
Nov 26, 2014
KasperBrandt
added a commit
that referenced
this issue
Nov 26, 2014
KasperBrandt
added a commit
that referenced
this issue
Nov 26, 2014
[#912] Fixed Group spelling error in migration 0071
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement django-guardian
The text was updated successfully, but these errors were encountered: