Choose the server and invitation link
Use your organization’s meeting server if one was provided. A room name on meet.example.com does not identify the same meeting as that name on meet.jit.si. Start with the joining guide if you have only a room name. [S1]
For a new session, choose a distinctive name using the server’s normal meeting flow and copy the full invitation link. Avoid predictable names and public sharing for a private call. Jitsi’s usual rooms exist while people are present; a link written in a calendar is not a reserved room or proof that you own its name. [S1][S2]
On meet.jit.si, the person starting the room must authenticate. A calendar organizer and a Jitsi moderator are different roles: inviting guests does not supply the server login or a token that your private deployment may require. Confirm who will start the meeting. [S1]
This guide was checked against current provider documentation and Jitsi Meet 11248 source on 27 October 2026. It describes preparing invitations, not a completed calendar integration or live meeting test. [S3][S4][S5]
Add Jitsi to Google Calendar
- Create an event in Google Calendar and enter its title, start and end time. Check the event’s time zone, especially for international guests.
- Put the complete Jitsi link in the event description, with a short instruction that this is the meeting guests should join. You can also use the location field when appropriate.
- Add your intended guests. Before saving, inspect the conferencing area: a work or school calendar can add Google Meet automatically. Remove an unintended conferencing link if your account allows it, or ask the calendar administrator, so guests have one clear destination. [S3]
- For a series, open Does not repeat, choose the frequency and set the series end. Check a later occurrence as well as the first one. [S4]
- Review the complete invitation before saving and sending it. Ask a guest to confirm that their received event contains the right domain, link and local time.
Manual link sharing does not require connecting Jitsi to your calendar. The optional Jitsi Meet for Google Calendar add-on is published by 8x8 for meet.jit.si. Review its requested permissions and your organization’s installation policy if you choose that route. Its listing does not establish compatibility with an arbitrary private Jitsi server. [S5]
Add Jitsi to Outlook
In new Outlook, create a New Event, enter the attendees and date/time, and put the complete Jitsi invitation link in the event body. Inspect the Teams meeting toggle and any automatically inserted conferencing details; turn off an unintended Teams meeting when available. For repeated sessions, select Recurring, choose the interval and save the repeat settings before sending the invitation. [S6]
In classic Outlook, create a meeting request, add the details and Jitsi link, then use Meeting > Recurrence for a series. Review the recurrence range and send the invitation. New Outlook and classic Outlook have different controls, so follow the tab matching your version in Microsoft’s scheduling instructions. [S6]
If the Jitsi link changes, update the intended occurrence or series and send the calendar update. Confirm that guests are opening the revised event rather than an older forwarded invitation. Google also asks which events in a repeating series an edit should affect. [S4][S6]
Reusing a link does not preserve every meeting setting
The same link can be convenient for a standing team call, subject to the hosting service’s policies. It also remains known to anyone who received it before. Use a new distinctive link when the audience changes or the old link has been shared too widely. [S2]
In Jitsi’s usual lifecycle, the meeting ends when the last person leaves. Opening the same name later creates a new meeting, and the ordinary room password is reset. Do not print a password in a months-long invitation and assume it remains active. Join early, confirm the actual access rules and set the required password again for the new session. Custom deployments can add their own persistence or admission rules. [S2]
Use the login, moderator and password guide when a guest sees an access prompt. A calendar invitation is not a substitute for server authorization, a current room password or lobby admission. [S1][S2]
For longer public-service sessions, read the meet.jit.si 95-minute limit. Making the calendar event longer does not change that limit. Plan the break and a new meeting link in the invitation instead of promising uninterrupted access. [S7]
A clear invitation checklist
Include the full meeting URL, date, start and end time, time zone, organizer contact route and any instructions for waiting for the host. Share access information only with the intended audience. Avoid putting a private link or password in a publicly visible calendar. [S1][S2]
Before the first session, check:
- The received invitation has one unambiguous conferencing destination.
- A guest in another time zone sees the expected local time.
- The organizer can start that exact server and room.
- Guests know where to obtain the current password or ask for admission.
- A future recurring occurrence has the intended link and schedule.
- Phones open the correct full link; see the mobile app guide for private-server selection.
These are recommended acceptance checks, not tests completed by this site. No invitation was sent, add-on installed or calendar permission granted during this review.
When the invitation does not work
| Symptom | First check |
|---|---|
| Guests enter Google Meet or Teams instead | Inspect automatically added conferencing details and the link in the received invitation. [S3][S6] |
| Guests arrive in an empty room | Compare the complete domain and room with the current event, then check the time and organizer’s presence. [S1] |
| Yesterday’s password is rejected | Ask which password was set for this new session; ordinary room passwords do not persist after everyone leaves. [S2] |
| No calendar connection button appears inside Jitsi | The reviewed web integration needs enableCalendarIntegration plus a Google or Microsoft application client ID. Manual invitations do not need that optional integration. Ask the operator rather than granting unrelated permissions. [S8] |
| One occurrence still has the old link | Check whether the edit applied to that occurrence, future events or the whole series. [S4][S6] |
Sources and maintenance
- [S1] Official starting instructions, checked 27 October 2026, including first-person authentication. Private services can differ.
- [S2] Jitsi security and privacy, checked 27 October: room lifecycle, name exposure and password reset. Used for those principles, not its historical UI screenshots.
- [S3] Google Calendar event creation, checked 27 October: event details and automatically added Meet conferencing.
- [S4] Google Calendar recurring events, checked 27 October: repetition and editing a series.
- [S5] 8x8’s Jitsi Google Calendar listing, checked 27 October, listing updated 20 October. Optional integration, not an installation test.
- [S6] Microsoft’s new and classic Outlook meeting instructions, checked 27 October.
- [S7] Official meet.jit.si service change, 9 October 2026.
- [S8] Meet 11248 calendar availability check. Recheck provider UI, hosting rules and optional integration configuration when they change. No event, device, server or meeting test claimed.