[How to] What is a meeting moderator?

What is a meeting moderator? What can a moderator do? How is this role assigned? This post will help you understand more about the Jitsi Meet room moderators.

Moderator Permissions

What can a moderator do?

  • Ability to add a password to a room
  • Ability to grant the moderator role to non-moderators
  • Ability to kick non-moderators (and other moderators only if muc_owner_allow_kick.patch is applied)
  • Ability to mute participates
  • Ability to make everyone see the moderator video (Everyone follows me)
  • Ability to make participates join muted (Everyone starts muted)
  • Ability to make participates join without video (Everyone starts hidden)
  • Ability to enable/disable the lobby room
  • Ability to approve join/knocking requests (when the lobby is enabled)
  • Ability to enable e2e encryption • beta (where available)

:x: A moderator CANNOT unmute another participant’s audio or video.

Who is a moderator?

When someone joins, who gets the moderator role?

For the default install:

  • first participant to join is moderator
  • when the moderator leaves, a new one is selected automatically
  • selection occurs on the server side (by Prosody & Jicofo)

For the default install with secure domain:

  • All authenticated users are moderators
  • Guest users are not moderators and cannot create rooms

With mod_muc_allowners.lua enabled:


I noticed this feature after your post :+1:

So I need everybody to be a moderator by default and don’t want to enable secure domain as well. I am running the latest build (installed like 6 hours ago) and have enabled ‘muc_allowners’ inside prosody conf but it’s not working. Could you please help?


I have also experienced issues with the current version of mod_muc_allowners.lua where it seems others do not.

My post in this thread may help you/others:

1 Like

Thank you so much!! Your solution worked like a charm.

Hey Corby may I know How to do this?

If you know how could you please tell me (Screenshots would be appreciated)

1 Like

when the meeting is on, You can select any participant and grant them the moderator rights. Please check the screen below

Hi, I can’t find anywhere about grant moderator.
I would like to try this function and checkout sourcecode.
Could you give a recommend?

How do I disable this in the meet.jitsi.si?

You can’t. You’d have to host your own server or get an 8x8 subscription - https://jaas.8x8.vc

Would self hosting still have access to the calling in numbers?

If you mean the dial-out feature, yes you can deploy Jigasi for that.

1 Like

I mean for people to join conference by phone, not to call out.

Yes, it’s the same component.

Thank you, now I have more research to do LOL.

I’m currently struggling on making a JWT Authentication valid on my custom deploy with Docker. I have secure domain configured, certificates works, and JWT authentication is working. Users can call each other and everything is working as intended (except for the timer, but it’s for another thread).

But, as for default install with secure domain, all users with a valid JWT are becoming moderators. I installed the Affiliation Plugin for checking who is who, and it’s working, but “something” overwrites my preferences about affiliation immediatly after user will join and every user become a moderator anyway.

Where can I customize the “default behavior” or the secure domain on a Docker Deploy? How to make only moderator became moderators and make stay member as a simple member?

PS: Please remember that my JWT is valid and my mod_affiliation works as expected, until it’s not because affiliation is overwritten by someone, as told here

1 Like

For those wondering how to do in kubernetes or docker(making everyone moderator)

  1. Add a environment variable for prosody
        - name: XMPP_MUC_MODULES
          value: muc_allowners

  1. Download “mod_muc_allowners.lua” file from internet and make a new prosody image from below dockerfile
FROM jitsi-prosody:latest
COPY ./mod_muc_allowners.lua  /prosody-plugins-custom/mod_muc_allowners.lua

  1. Re-Deploy all the service again with prosody new image create above
1 Like

This works for me. Thank you!

Please note that Jitsi in Docker has muc_allowners installed.
To enable it, modify this line in .env file.

# Custom Prosody modules for MUC component (comma separated); allowners module needed for all users have moderator rights


And run
docker-compose up -d --force-recreate web