Skip to content

Implement permissions to control public and registered members permissions management #13578

@sijandh35

Description

@sijandh35

In view of the removal of ADW from GeoNode (#13472) we want to replace its publishing and approval mechanism by implementing the option to control if the current GeoNode user can change or not the permissions for the two "special" groups, Anonymous, and Registered Members.

Proposed Changes:

  • Introduce two new permission types
    • can_manage_anonymous_permissions
    • can_manage_registered_member_permissions
  • These two permissions will be treated the same as the other permissions, through the Permissions Registry and the default permisisons handler and will be returned by the permissions serializers inside the API responses
  • By default the the resource owner and any user with edit permissions on the resource will be assigned both permissions
  • Two new settings will allow for restricting the permissions. If set to False, only an administrator or a user with user.is_staff set will be assigned those permissions
    • EDITORS_CAN_MANAGE_ANONYMOUS_PERMISSIONS= False # default value
    • EDITORS_CAN_MANAGE_REGISTERED_MEMBERS_PERMISSIONS = False # default value

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions