Moderation¶
mod_jitsi gives moderators full moderation control over a session: they can mute participants, disable their cameras and remove (kick) participants from the room.
Who becomes a moderator is determined by the Jitsi Moderation
(mod/jitsi:moderation) capability. Users granted this capability are promoted to
moderators; when the session runs in token-based mode, a moderator indicator is shown
next to their name.
Token-based mode is recommended¶
There are two ways moderation can be enforced, depending on how the Jitsi server is configured.
| Mode | Behaviour |
|---|---|
| Token-based (JWT) | Only users with the mod/jitsi:moderation capability are sent as moderators. Only they can mute participants, disable cameras or remove participants. A moderator indicator is displayed next to their name. |
| Without token | Moderation buttons such as mute everyone or kick participant are hidden from non-moderator users — but experienced users may be able to bypass these client-side restrictions. |
Use token-based mode for robust moderation
Without a token, moderation relies on hiding buttons in the interface, which can be circumvented. For production deployments, run your Jitsi server in token-based (JWT) mode so that moderation privileges are enforced server-side and cannot be bypassed.
See Token-based mode (JWT) for how to set this up.
Granting moderation¶
Assign the Jitsi Moderation (mod/jitsi:moderation) capability to the roles that
should moderate sessions. This capability is available at the activity level, so teachers
can override the default for a specific activity.
Self-hosted servers
On a self-hosted Jitsi server with JWT authentication you must install the
jitsi-token-moderation-plugin on the server for moderator roles to be honoured.
Without it, the moderator field in the token is ignored and every user joins as a
moderator. This is not needed for 8x8 JaaS or GCP auto-managed servers, where
moderation is handled natively. See Token-based mode (JWT).