v2.3.3 - June 24th
2 min
this release brings a new notification center and requests for information to reporters giving moderators richer context and tighter collaboration it also makes notes and custom attributes easier to manage, refines the debug reports experience, and fixes the review timer new features in nima notification center moderators now have a dedicated notification center inside nima that alerts them when they're @mentioned in case notes unread alerts are badged, and each notification deep links straight to the relevant case so moderators can respond without hunting for context you can mark notifications as read or unread, delete them, and manage them individually or in bulk — keeping collaboration tight and nothing falling through the cracks requests for information to reporters the request for information (rfi) flow now reaches reporters, not just reported accounts reporters receive an email prompting them to provide more detail via a nima form, and their responses appear as a chat thread directly on the case this makes it far easier to gather the context needed to make a confident moderation decision improvements content level moderator notes notes are now attached to content rather than to individual reports, so a note written on one report is visible across every report about the same content moderation teams get a single, consistent thread of context, avoiding duplicated effort when the same content is reported multiple times custom attribute queue visibility admins can now control which queues display a given custom attribute directly from the custom attributes settings page, complete with queue counts and quick selection this removes the need to edit every queue individually and makes configuration much faster unified request for information experience the rfi experience is now consistent across the report and appeal consoles, with shared context bubbles and indicators so moderators get the same familiar flow wherever they're working fixes & stability report timer reset the review timer now resets correctly for each report, so moderators no longer see premature timeout warnings when they've just opened a case