How to hide links in more actions menu in config.js?

Hello there,
how can i deactivate some menu items from the more actions menu? I found the code in /usr/share/jitsi-meet-web-config/config.js and deleted everything i wanted. But i see still the defaults. Am i in the right file?

It looks like this:
toolbarButtons: [
‘microphone’, ‘camera’, ‘closedcaptions’, ‘desktop’, ‘embedmeeting’, ‘fullscreen’,
‘fodeviceselection’, ‘hangup’, ‘profile’, ‘chat’, ‘etherpad’, ‘settings’, ‘raisehand’,
‘videoquality’, ‘filmstrip’, ‘invite’, ‘feedback’, ‘shortcuts’,
‘tileview’, ‘select-background’, ‘download’, ‘help’, ‘mute-everyone’, ‘mute-video-everyone’, ‘security’

Anyone an idea? Would be great to know
Thanks in advance.

Is there a TOOLBAR_BUTTONS line in your /usr/share/jitsi-meet/interface_config.js?

Hello Emrah,
in the new version it moved to the folder meet-web-config. What i can see is that as a moderator i see the complete nav items. As a user i see only a few. But it seems, that it is not the selection i provided.
Strange thing. Or is it not working in this release. Anybody an idea?

Thanks again,

Shouldn’t the file to edit be
/etc/jitsi/meet/DOMAIN–config.js ?

Yes. That is what it looks like in the new version:

* This config was moved to config.js as toolbarButtons.
// ‘microphone’, ‘camera’, ‘closedcaptions’, ‘desktop’, ‘embedmeeting’, ‘fullscreen’,
// ‘fodeviceselection’, ‘hangup’, ‘profile’, ‘chat’, ‘recording’,
// ‘livestreaming’, ‘etherpad’, ‘sharedvideo’, ‘settings’, ‘raisehand’,
// ‘videoquality’, ‘filmstrip’, ‘invite’, ‘feedback’, ‘stats’, ‘shortcuts’,
// ‘tileview’, ‘select-background’, ‘download’, ‘help’, ‘mute-everyone’, ‘mute-video-everyone’, ‘security’
// ],

When you access, do you see your edited version of config.js?

also, which links are you attempting to remove?

Hello shawn, yes i see all my changes. But the changes for the custom menu are missing. I would like to hide recording, stats, live stream, share audio, share video. I think i´m editing the wrong file.

Thanks for your response!

All the best,


Where are you checking - desktop or mobile?


You’re editing the wrong file. You should be editing /etc/jitsi/meet/your.domain-config.js

I did, but it is not working. And it´s really complicated, because you have to look for each item. It´s not so easy as the old version.

// Local Recording

// localRecording: {
// Enables local recording.
// Additionally, 'localrecording' (all lowercase) needs to be added to
// TOOLBAR_BUTTONS in interface_config.js for the Local Recording
// button to show up on the toolbar.
//     enabled: false,

// The recording format, can be one of 'ogg', 'flac' or 'wav'.
//     format: 'flac'

// },

Hmm… unless I’ve missed something, toolbarButtons in config.js should work the same way as the deprecated TOOLBAR_BUTTONS.

The localRecording section that you quoted controls whether that feature is actually supported but does not influence to icons in the toolbar.

Would you be able to share what you see in (the actual file you get when you access it from browser)?

I´m sorry for not responding so quick. The solution is super easy. You where right. Everything is in the But every Action Button seperatley. I wasn´t awary of it. Sorry for such a waste of time…

If someone is looking for it. It looks like this:

// Recording

// Whether to enable file recording or not.
fileRecordingsEnabled: false,
// Enable the dropbox integration.
// dropbox: {
//     appKey: '<APP_KEY>' // Specify your app key here.
//     // A URL to redirect the user to, after authenticating
//     // by default uses:
//     // ''
//     redirectURI:
//          ''
// },
// When integrations like dropbox are enabled only that will be shown,
// by enabling fileRecordingsServiceEnabled, we show both the integrations
// and the generic recording service (its configuration and storage type
// depends on jibri configuration)
// fileRecordingsServiceEnabled: false,
// Whether to show the possibility to share file recording with other people
// (e.g. meeting participants), based on the actual implementation
// on the backend.
// fileRecordingsServiceSharingEnabled: false,

// Whether to enable live streaming or not.
liveStreamingEnabled: false,