LSEED connects your own Zoom account to its event reservation feature. Once connected, events that members book in LSEED are hosted on Zoom automatically: LSEED issues the meeting or webinar, delivers the join link, records who attended, and can import the cloud recording so that attendees can replay it inside LSEED.
This guide covers adding the integration, using it, and removing it.
Before you start
- An LSEED account. You need permission to open 設定 → API連携設定 (Settings → API Integration). Account owners have this by default; other users need the API permission granted by the owner.
- A Zoom account. Each LSEED tenant connects its own Zoom account. You do not need a Zoom account provided by LSEED.
- For webinars: a Zoom plan that includes webinars. Without one, LSEED hides the webinar options.
- For recording import: cloud recording enabled on the Zoom account.
- If your Zoom account restricts app installation, your Zoom administrator may need to approve the app before you can connect.
1. Adding the integration
Start the connection from LSEED, not from the Zoom App Marketplace "Add" button. On the app's Marketplace page the button is labelled Visit Site to Add and it brings you to LSEED.
- Sign in to LSEED.
- In the left menu open 設定 → API連携設定 (Settings → API Integration), at
/settings/api-coordination. - Click the Zoom card and enter any name you like for this connection. The name is only used to tell connections apart inside LSEED.
- Continue to Zoom and approve the authorization screen.
- You are returned to the API Integration list, where the connected account's email address is shown.
LSEED then checks what the connected account can do — whether cloud recording is available and whether webinars are available — and enables or hides those features accordingly.
What LSEED asks for and why
| Permission | Why it is needed |
|---|---|
| Read your user profile and settings | Identify the connected account, prevent it being connected twice, and detect whether webinars and cloud recording are available |
| Create, read, update and delete meetings | Issue the meeting for an event booking slot, reflect reschedules, and remove it on cancellation |
| Create, read, update and delete webinars, and manage registrants | The same for webinars, plus registering a booked member so Zoom issues a personal join link, and cancelling that registration |
| Receive participant-joined events | Mark the matching booking as attended |
| Read cloud recordings | Import the recording of a session hosted through LSEED so attendees can replay it |
You can connect more than one Zoom account. Each meeting setting in LSEED specifies which connection it uses. Within one LSEED tenant, the same Zoom account cannot be connected twice.
2. Using the integration
2.1 Create a meeting or webinar setting
- In the left menu open スケジュール → ミーティング管理 (Schedules → Meetings), at
/schedules/zoom-meetings. - Click 新規作成 (New), choose ミーティング (Meeting) or ウェビナー (Webinar), select the Zoom connection to use, fill in the title, date, time and options, and save.
LSEED creates the meeting or webinar in Zoom at this point, and shows its ID and join URL in the list.
If you edit a saved setting, LSEED updates it in Zoom and then re-reads it. This matters when you
change the passcode: Zoom replaces the pwd value inside the join URL, and LSEED needs the new URL
so that it never distributes a stale one.
2.2 Use the setting in an event
- Open スケジュール → イベント設定 (Schedules → Event settings), at
/schedules/event-setting. - Create an event and set the venue type to Zoomミーティング予約 (Zoom meeting booking) or Zoomウェビナー予約 (Zoom webinar booking).
- Choose the Zoom connection and the meeting setting created in 2.1, add time slots, and publish the event.
2.3 What a member receives
When a member books a slot:
- Meeting booking: LSEED issues the meeting for that slot, or reuses a shared one.
- Webinar booking: LSEED registers the member with Zoom and receives a personal join link for that member.
The join URL and passcode are included in the booking confirmation sent to the member, and are
shown to you on the booking detail page at /schedules/appointment-detail/{id}.
2.4 Changing or cancelling a booking
- Moving a booking to another slot re-points it at that slot's meeting. For webinars, LSEED re-reads the member's personal join link so the member always receives the correct URL.
- Cancelling a booking cancels the webinar registration, or deletes the meeting when the cancelled booking was the last one for that slot. The join URL and passcode are removed from the booking; the meeting ID is kept as part of the booking history.
2.5 Attendance
When a participant joins, Zoom notifies LSEED and the matching booking is marked 参加済み (attended), together with the first join time. Hosts and alternative hosts are excluded.
Automatic attendance from Zoom join notifications applies to meetings and webinars issued per booking slot. For a shared meeting or webinar used across multiple sessions, LSEED cannot identify the session from a join notification; after the session ends, its bookings are marked attended and the session start time is recorded. Attendance may also be changed manually on the booking detail page after the end time. LSEED stores only the attendance state and one timestamp per booking (the first join time when a notification is used, or the session start time otherwise). Identifiers in join notifications are used only to match a booking and are not stored.
2.6 Cloud recordings
If the session was recorded to the cloud, Zoom notifies LSEED when the recording is ready. LSEED downloads the MP4 into its media library and attaches it to that booking's archive, so the members who booked the event can replay it inside LSEED. Only MP4 and M4A files are stored, and only MP4 can be published.
Once a day, LSEED also checks for recordings whose notification never arrived — for example during maintenance — and imports the ones that are missing. Recordings of meetings that were not created through LSEED are ignored and are never downloaded.
3. Removing the integration
You can remove the integration from either side. Both do exactly the same thing.
3.1 From LSEED
- Open 設定 → API連携設定 (Settings → API Integration).
- Open the connection you want to remove and disconnect it.
3.2 From Zoom
- Sign in to the Zoom App Marketplace.
- Open Manage → Installed Apps (or search for the app and open its page).
- Click Remove.
3.3 What happens to your data
| Item | What happens |
|---|---|
| Access token, refresh token, authorization data | Deleted immediately |
| Cached feature-availability flags | Deleted immediately |
| The connection itself | Disabled. The account's email address, name and Zoom user ID are kept for audit purposes |
| Meeting and webinar settings that used the connection | Deactivated. They stop issuing new meetings |
| Join URLs already delivered to members | Removed from LSEED. Meetings already created in Zoom are not deleted by the removal itself |
| Imported recordings | Permanently deleted 7 days after removal — the media files, the archive entries and the records. You are notified in LSEED of how many files will be deleted and on what date |
| Bookings and attendance records | Kept. They are LSEED's own data, not Zoom's |
Reconnecting within 7 days cancels the deletion. If you connect the same Zoom account again before the grace period ends, the scheduled deletion of the imported recordings is cancelled automatically and the recordings stay available.
After the 7 days have passed, the recordings cannot be restored from LSEED. Recordings still held in your Zoom account are unaffected.
To request deletion of the identification data that is kept after removal, contact support@lseed.jp.
Troubleshooting
The webinar type cannot be selected. The connected Zoom account has no webinar license. LSEED hides the option rather than letting the call fail. Connect an account with webinars enabled, or reconnect after the license is added so LSEED re-checks the account.
A recording has not appeared. Zoom takes time to process a recording after the session ends, and the notification arrives only when processing finishes. If it still has not appeared the next day, the daily catch-up job will import it. Check that cloud recording was actually enabled for that session.
The API Integration page cannot be opened. The signed-in user has no API permission. Ask the account owner to grant it, or sign in as the owner.
The join URL changed. Changing the passcode on a meeting setting makes Zoom issue a new join URL. Members who booked before the change receive the updated URL in LSEED; re-send the booking confirmation if you distributed the URL by other means.
Data and privacy
LSEED stores the connected account's identification, the meetings and webinars it issued, attendance times, and imported recordings. OAuth tokens are encrypted before being stored. Recording files are stored in Amazon S3 with server-side encryption and delivered over Amazon CloudFront. Zoom data is not shared with third parties and is not used for AI/ML processing or model training.
See the Privacy Policy and the Terms of Use for details.
Support
Visit the LSEED Help Center or contact support@lseed.jp.