RocketChat / RocketChat/Rocket.Chat
[Feature] Add admin audit log for new user moderation actions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Is your feature request related to a problem?
Currently when admins manually mute, deactivate or flag a new user account, there is no centralised audit trail recording who took the action, when, and why. This makes it difficult to:
- Review past moderation decisions
- Identify patterns in spam behaviour
- Comply with community governance requirements
Describe the solution you'd like
A dedicated audit log under Admin > Moderation that records:
- Timestamp of action
- Admin who performed the action
- Action type (mute / deactivate / flag / dismiss)
- Target user account age at time of action
- Optional reason field
Additional context
This would serve as foundational infrastructure for automated anti-spam systems that need to log their decisions alongside manual admin actions.
- Saksham Jain (@jainsaksham2006), GSoC 2026 applicant
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the Admin > Moderation handlers for mute, deactivate, flag, and dismiss actions, then inspect any existing audit or activity-log patterns. Done means a centralized log records each requested field, including the optional reason, and is available under Admin > Moderation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100