You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2020. It is now read-only.
The group field was originally used for permissioning. That is data fields and concepts could be assigned to a group and only users who were part of those groups would be able to access those fields or concepts.
However, django-guardian is another mechanism for applying finer-grain permissions. The same strategy can be achieved above by assigning adding a permission to a group for the field/concept. Any users part of that group will have access to the fields/concepts.
Furthermore, in reviewing the code, the group field was never actually used in the published() manager method...
The text was updated successfully, but these errors were encountered:
The
group
field was originally used for permissioning. That is data fields and concepts could be assigned to a group and only users who were part of those groups would be able to access those fields or concepts.However, django-guardian is another mechanism for applying finer-grain permissions. The same strategy can be achieved above by assigning adding a permission to a group for the field/concept. Any users part of that group will have access to the fields/concepts.
Furthermore, in reviewing the code, the
group
field was never actually used in thepublished()
manager method...The text was updated successfully, but these errors were encountered: