Moderation Tools

Any user is allowed to flag a message. This triggers the message.flagged webhook event and adds the message to the inbox of your Stream Dashboard Chat Moderation view.

If you prefer to build your own in app moderation dashboard, rather than use the Stream dashboard, then the query message flags endpoint lets you get flagged messages. Similar to other queries in Stream Chat, you can filter the flags using query operators.

Both server-authenticated and user-authenticated clients can use this method. For client-side requests, the user needs moderator or an admin permissions. This default behavior is controlled by the ReadMessageFlags permission and can be customized if needed. Read our permissions documentation to learn more.

Pagination for message flags can be done using the offset/limit options. Flags are returned in ascending order of creation, starting from the most recent flag.

Any user is allowed to mute another user. Mutes are stored at user level and returned with the rest of the user information when connectUser is called. A user will be be muted until the user is unmuted or the mute is expired.

After muting a user messages will still be delivered via web-socket. Implementing business logic such as hiding messages from muted users or display them differently is left to the developer to implement.

Users can be banned from an app entirely or from a channel. When a user is banned, they will not be allowed to post messages until the ban is removed or expired but will be able to connect to Chat and to channels as before.

Users must be a member of a channel to be banned from that channel. Channel watchers cannot be banned.

It is also possible to ban the user's last known IP address to prevent creation of new "throw-away" accounts. This type of ban is only applicable on the app level. We do not recommend applying IP ban without reasonable timeout, however this is not restricted. The IP address will be unbanned either after reaching a timeout or with explicit user unban.

In most cases only admins or moderators are allowed to ban other users from a channel.

Banned users can be retrieved in different ways:

1. Using the dedicated query bans endpoint

2. User Search: you can add the banned:true condition to your search. Please note that this will only return users that were banned at the app-level and not the ones that were banned only on channels.

The query bans endpoint allows you to list bans for your application. Similar to other query endpoints, you can filter bans by different fields and control the ordering of results.

Pagination for bans can be done in two ways: using offset/limit or using the "created_at" field. Bans are returned in ascending order by default so to get the second page you need to request bans with "created_at" less than the created_at of the last ban in the first page. Ordering can be reversed using the sort option.

Users can be shadow banned from a channel, set of channels, or an entire app. When a user is shadow banned, they will still be allowed to post messages, but any message sent during the ban, will have the shadowed: true field set; this will be invisible from the author of the message.

You will need to implement UI logic for how your application will handle shadowed messages. Having the client hide these messages for everybody other than the user sending them is a common approach.

Administrators can view shadow banned user status in queryChannels(), queryMembers() and queryUsers().

A list of words you can define to moderate chat messages. A block list can be assigned to each channel type to either block or flag messages that contain these words. More information can be found here.

Advanced Chat Moderation uses an AI-based classification system to detect various types of bad content. The tool is powered by a machine learning model that provides a confidence interval (0-1) for a message, in each of three categories: Spam, Explicit and Toxic. The model is highly configurable for each channel type and removes the manual work of a human moderator. You can learn more here.