For context, I am using Jitsi-as-a-Service, and the iFrame API, and right now, I’m generating URL’s with a JWT passed into it containing user info, etc. via query param.
Recently, after browsing through the forums, I learnt it was possible to actually pass in
interfaceConfigOverwrite attributes into the meeting URL using
# URL fragments. ([How to] How to customize meeting options)
My question is, which of the settings in
config.js (jitsi-meet/config.js at master · jitsi/jitsi-meet · GitHub) or
interface_config.js (jitsi-meet/interface_config.js at 76b4899c3966b1c8c972e029169735ae9330edbb · jitsi/jitsi-meet · GitHub) are actually working via a URL fragment? Have all of them been tested to work?
Some examples of config options I need are:
- Being able to turn off all notifications (possible via iFrame API)
- Automatically enabling lobby as soon as moderator joins (possible via iFrame API)
- Being able to disable invite toolbar buttons (also possible via iFrame API)
All of these options I have only so far been able to achieve using the embedded iFrame, but not yet in external meeting links.
As such, how would I go about adding this to the URL fragment if ever, especially if said option is normally passed as an array rather than individual key-value pairs?