Oh, yes access code is a bit missleading. The groups that are created in galene server always using a JWT Token hidden from the user. The plugin generates links for every group and every role (presenter, ...) but this link points to the plugin host. The plugin checks the request for authentication details, that are store in the plugins database. These authentication details are configured by the administration UI of the plugin. For ervery Galene role the following auth mechanism can be configured: - dedicated username/password from the plugins users database - logged in in Wordpress with an allowed role- needs to know a 6 digit number that is generated randomly from the plugin- nothing at all - free access for everyone If this is checked by the plugin (e.g. for the first case it asks for a username/password) then the request is redirected to the configured Galene Server including the immediately generated JWT token. As an example a room/group can be configured following:- others: free access- presenters: 3 users from the plugins users database- op: Wordpress administratorsThats an example for an free audience, where 3 people are active speakers and the Wordpress administrator is op. Or as an alternative others have to know a 6 digit number than its a bit more limited. But all need to know the url's. In this example there are three urls (others,presenter,op) that are all pointing to the plugins host (and will be checked there). Hopefully that explains it a bit more? For sure one of the tasks on my list is to write some (more) documentation. P.S.: on Github in the subfolder docker there is a docker-compos.yml that should run a demoinstallation with some preconfigured rooms/groups Best Regards,