Community Membership Log

[azurelunatic]

Title:
Community Membership Log

Area:
communities, community administration

Summary:
For community administrators: Log relevant community membership changes, such as new members joining, moderated membership activity, members leaving, attribute changes (post moderation, post permission, moderator, admin), and bans.

Description:
Some of these attributes are already logged for site administrators, but it would be useful to have them logged for community administrators.

Invitation -- username of invitee, server time of action, username of admin making the invitation.

Join -- username of member, server time of action, and whether it was in response to an invitation/through the member moderation (and who approved the membership if so).

Membership rejection -- username of applicant, server time of action, username of admin rejecting the application.

Invitation expiration -- username of invitee, server time of invitation & expiration, username of admin who invited them.

Attribute change -- username of member, server time of action, the change (gained/lost post, entry moderation, moderation power, admin power), and username of admin.

Ban/unban -- username, server time of action, ban/unban, username of admin.

Departure -- username, server time of action, and username of admin if this was an admin action.

Should reading page subscription/unsubscription also be logged?

Poll #9396 Community Membership Log

Open to: Registered Users, detailed results viewable to: All, participants: 62

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
38 (61.3%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
24 (38.7%)

(Other: please comment)
0 (0.0%)

Comments

[turlough]

I've been wanting something like this forever!

[azurelunatic]

Ooo, invitations should also have the attributes that they were invited under. And joins should have attributes that were assigned to them upon joining.

[azurelunatic]

And departures, the attributes that they had at the time of departure.

[susanreads]

Isn't reading page subscription/unsubscription something you can track anyway, or is that only for personal journals?

[turlough]

Only for personal journals. I made a suggestion some time ago that mods should be able to do it for comms and I think it was migrated to Bugzilla but I don't know what has happened with it since then.

[denise]

http://dw-suggestions.dreamwidth.org/?poster=turlough will give you your former suggestions if you want to look it up!

[turlough]

Thank you! I keep forgetting that exist.

[marahmarie]

Oh, that's awesome, I never knew there was an all-in-one-link for that before. Thanks, Denise. :)

[azurelunatic]

Only for personal journals, and unsubscription is only for paid.

[azurelunatic]

In any case, having it all in one place as a log addresses a slightly different need than being notified immediately about it when it happens. Notifications are good for something that someone needs to know about, often in order to take action or be generally aware -- for a personal journal, in the event of a new subscriber or access, go take a look and maybe add them back; someone drops you, consider if it's mutual, if it's a friend, see if there's anything that needs patching up -- but logs are good for going and looking up what happened when -- have we really known each other forever, did we exchange access before or after you made that one entry, etc.

Community admins don't often need to do much of anything when someone enters or leaves, so it might just be so much noise for them, but a log of when something happened, so they can figure out how long someone's been in a community, notice the sudden flurry of unsubscriptions after that amazingly bad decision, notice the sudden flurry of joins after making a comment in dw_news, et cetera.

[susanreads]

Oh yeah, that makes sense!

[arethinn]

I'd love to be able to see this kind of stuff as a community admin.