Filament

The free plugin is enough to manage comments, reports, and settings. Pro is additive. It never replaces those resources. Install Filament in the app, then register the free plugin:

composer require filament/filament:"^4.0|^5.0"
php artisan filament:install --panels

use Filament\Panel;
use Usamamuneerchaudhary\Commentify\Filament\CommentifyPlugin;

public function panel(Panel $panel): Panel
{
    return $panel->plugin(CommentifyPlugin::make());
}

A render hook that closes over one model keeps showing that model’s comments. Put the thread on the form instead. It stays hidden while you are creating, and remounts when the modal opens a different record.

use Usamamuneerchaudhary\Commentify\Filament\CommentsEntry;

public static function form(Schema $schema): Schema
{
    return $schema->components([
        CommentsEntry::make(),
    ]);
}

The same call works on a relation manager form. The entry reads the record Filament has open. Filament v4 and v5 both work. Publish commentify-filament-views only when you need to change the admin markup. With approval on, the Comments resource has Approve and Disapprove actions, the same bulk actions, and an approval-status filter (approved, pending, all). The Commentify Settings page toggles most core flags. allow_guests stays in config. Register Pro beside it when you want the queue, spam log, and audit trail:

use Usamamuneerchaudhary\Commentify\Filament\CommentifyPlugin;
use Usamamuneerchaudhary\CommentifyPro\Filament\CommentifyProPlugin;

public function panel(Panel $panel): Panel
{
    return $panel->plugins([
        CommentifyPlugin::make(),
        CommentifyProPlugin::make(),
    ]);
}

The installer detects a missing CommentifyProPlugin in app/Providers/Filament/*.php and prints this snippet rather than rewriting the provider (a mangled panel file would take the whole admin down). Filament is optional. composer.json suggests filament/filament ^4.0|^5.0.

Free plugin (core)

Comments: edit, delete, approve / disapprove, bulk actions, filters (user, parent/child, approval)
Comment reports: pending / reviewed / dismissed, reporter, reason, IP
Commentify Settings: most core flags from the panel (allow_guests stays in config)

Pro plugin

Navigation group Commentify.

Moderation queue (`commentify-moderation-queue`)

Same Comment model, dedicated table. Badge shows pending count. Columns: id, author (Guest if none), body excerpt, type, rating, accepted, approved, reports badge, commentable type, created at. Filters: pending only, has reports, contains links (http in body), commentable type, unanswered questions, reviews missing a rating. Record actions:

Action	Behaviour
Approve / Unapprove	Sets `is_approved`; writes audit
Ban author	`comment_banned_until` + 30 days (users only, not guests)
Pin / Unpin	One parent pin per thread
Accept / Unaccept	Q&A replies; same policy as the API
Draft reply	Queues a BYO-key AI draft (pending until approved). See AI.

Bulk: approve, unapprove, delete, ban. All go through Moderator so the audit log cannot drift.

Spam log (`commentify-spam-logs`)

Pipeline verdicts (review / deny), excerpt, checker, reasons, user id. Not spam: re-approves the matched held comment and submits ham to Akismet. See Spam pipeline.

Moderation audit (`commentify-mod-actions`)

Who did what: approve, unapprove, delete, ban_author, not_spam, not_spam_unmatched, plus pin / unpin from the queue. Moderator name, comment id, timestamp. The table filter lists the first five; pin rows still appear in the log.

Guest bans (`commentify-guest-bans`)

Ban a guest by email, IP, or both. A hard ban cancels the post. A shadow ban saves it with is_approved = false. Signed-in users are not matched here. User bans stay on the moderation queue Ban author action. An empty until keeps the ban until you delete the row. A past until makes it inactive. See Guests.

Unread comments

UnreadCommentsColumn is not on the moderation queue. Add it to your own table when a record should show how many parent comments are newer than the last time that user opened the thread.

use Usamamuneerchaudhary\CommentifyPro\Filament\Tables\Columns\UnreadCommentsColumn;

UnreadCommentsColumn::make();

The second argument is the thread name. The default is default. Opening the Livewire thread, or listing comments in the API, marks that thread read for the signed-in user.

Widgets

Pending moderation stat (cached count of is_approved = false)
Comments per day chart

Registering the plugin adds these to the panel. They sit on the dashboard with your other widgets.

Policies

Filament actions should remain consistent with Livewire and the API: same CommentPolicy, same bans. Do not bypass Moderator if you add custom actions. That class is the audit funnel.

Commentify

Commentify Pro

Frontends

API

Moderation

Features

Help

Free plugin (core)

Pro plugin

Moderation queue (`commentify-moderation-queue`)

Spam log (`commentify-spam-logs`)

Moderation audit (`commentify-mod-actions`)

Guest bans (`commentify-guest-bans`)

Unread comments

Widgets

Policies

​On an edit form or modal

​Free plugin (core)

​Pro plugin

​Moderation queue (commentify-moderation-queue)

​Spam log (commentify-spam-logs)

​Moderation audit (commentify-mod-actions)

​Guest bans (commentify-guest-bans)

​Unread comments

​Widgets

​Policies

On an edit form or modal

Free plugin (core)

Pro plugin

Moderation queue (`commentify-moderation-queue`)

Spam log (`commentify-spam-logs`)

Moderation audit (`commentify-mod-actions`)

Guest bans (`commentify-guest-bans`)

Unread comments

Widgets

Policies