Jitsi Meet Integration

Prerequisites

• A Jitsi Meet server you run, reachable by you and your guests
• For token authentication (optional): access to the server's Prosody configuration, or to the environment file of a Docker installation

Tymeslot never contacts your Jitsi server when you add the integration or when someone books; it only builds the links. The one exception is Test connection on the dashboard, which refuses a server at a private address unless a self-hosted Tymeslot sets ALLOW_PRIVATE_IPS_FOR_VIDEO=true. A Jitsi server on an internal network therefore works, on the managed service too, for every participant who can reach it.

How It Works

1 Connect your Jitsi server

1. Go to Dashboard → Integrations → Video.
2. Click Connect a video provider and choose Jitsi Meet under Self-hosted.
3. Give the integration a name if you want something other than the default.
4. Enter your server's address in Server URL, for example https://meet.example.com
5. If your server lets anyone in, leave App ID and App secret blank. If it uses token authentication, complete Step 2 before saving.
6. Click Add Integration.

Expected result: your Jitsi server appears in your list of video integrations.

2 Add token authentication (optional)

Skip this step if your server admits anyone. Otherwise, Tymeslot needs the same App ID and secret your server checks tokens against. On a server installed from packages, they sit in the Prosody configuration for your Jitsi domain, usually /etc/prosody/conf.d/meet.example.com.cfg.lua :

VirtualHost "meet.example.com"
    authentication = "token"
    app_id = "your_app_id"
    app_secret = "your_app_secret"

On a Docker installation, the same values are environment variables in your .env file:

ENABLE_AUTH=1
AUTH_TYPE=jwt
JWT_APP_ID=your_app_id
JWT_APP_SECRET=your_app_secret

Enter the App ID in App ID and the secret in App secret. Tymeslot needs both or neither: it refuses one without the other.

The secret must be at least 32 characters

Every link Tymeslot sends to a guest carries a token signed with this secret. Anyone holding one of those links can try guessing secrets offline, as fast as their hardware allows, until one produces the same signature. A long random secret puts that out of reach; a short one does not. Tymeslot therefore requires a secret of at least 32 characters (bytes) and refuses a shorter one. If yours is shorter, generate a new one on the server and update your Jitsi configuration first:

openssl rand -hex 32

What Tymeslot does with the credentials

• It signs one token for you and one for your guest, and adds each to that person's link as ?jwt=…
• Each token admits its holder to that booking's room only, never to other rooms on your server
• Each token expires four hours after the meeting's scheduled start, so an old link cannot be reused later
• Each token carries the person's name and email address, so they appear under their own name in the meeting

Who becomes moderator

Your token marks you as moderator and your guest's does not. A standard Jitsi server ignores that marking:

• On a Debian or Ubuntu installation with jitsi-meet-tokens , whoever joins first becomes moderator, guest or not.
• On docker-jitsi-meet with AUTH_TYPE=jwt, everyone holding a token becomes moderator.

For the marking to decide who moderates, configure your server as follows:

1. Run Jitsi Meet stable release 10978 (May 2026) or later.
2. Add token_affiliation to the main MUC component, beside token_verification . On Docker, add token_affiliation to XMPP_MUC_MODULES (comma-separated).
3. Turn off Jicofo's automatic moderator with jicofo.conference.enable-auto-owner = false . On Docker, set ENABLE_AUTO_OWNER=0 and also JICOFO_ENABLE_AUTH=0 .
4. If you use muc_wait_for_host , set wait_for_host_disable_auto_owners = true . On Docker, set WAIT_FOR_HOST_DISABLE_AUTO_OWNERS=true.

With that in place, you are moderator whenever you are in the room. A guest who arrives early waits without moderator controls until you join.

3 Enable Jitsi on a meeting type

Each meeting type chooses its own video provider. Repeat these steps for every meeting type that should use Jitsi:

1. Go to Dashboard → Meeting Types and pick a meeting type.
2. In the Location section, choose Video Meeting.
3. Under Select Video Provider, select your Jitsi integration.
4. Save.

Expected result: the next booking on this meeting type carries its own room link on your Jitsi server.

❓ Frequently Asked Questions

Verify the integration is working

• On Dashboard → Meetings, the booking shows a Join Meeting button that links to a room on your Jitsi server
• The booking confirmation email contains a link to the same room
• With token authentication, the links in your email and your guest's email each end in a different ?jwt=… value
• Opening your personal link from the confirmation email loads the Jitsi room without asking anyone to sign in