#1791 - Split up assume_any_member/member_maintenance privileges

Identifier #1791
Issue type Feature request or suggestion
Title Split up assume_any_member/member_maintenance privileges
Status Open
Tags

Roadmap: Over the horizon (partial implementation) (custom)

Handling member Deleted
Addon core_permission_management
Description These privileges conflate quite a few things. It's fine for most sites, but when you need granular control of user accounts in corporate environments of many teams, it isn't good enough.

Specifically...

(This is organised as <General task> >> <new privilege> >> <filename(s) needing changing>)

Need individualised privileges for what was assume_any_member(+enforce_personal_access)
change_any_group_memberships
admin_cns_join
cns_members_action2
settings
manage_any_ecommerce_history
invoices
shopping
subscriptions
classifieds
delete_any_account
delete
view_personal_calendar
calendar
view_member_warnings
warnings
view_member_files
filedump
Mention that assume_any_member includes changing password
Stop using assume_any_member as a secondary route to where member_maintenance also allows the same access (unnecessary complexity - just let admin grant additional privileges if needed, doing so wouldn't hurt anything)
Need individualised privileges for what was member_maintenance
edit_any_member
admin_cns_join
all the member setting hooks
reveal_email_addresses
members
CNS_MEMBER_PROFILE_ABOUT
cns_members_action2
ban_member
warnings
cns_members_action2
provide_minor_member_perks
settings
cns_members_action2
validate_any_member
settings
cns_members_action2
Get rid of member_maintenance privilege entirely
Steps to reproduce

Funded? No
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated