- Shipped
- November 7, 2026 at 7:35 PM UTC
- Author
- Kamo
- Commit
- 5097c48
Owner 2026-11-07: meeting providers are configured on Provider Setup; SIE10's separate "SI Meeting Joins" tab duplicated its provider cards, setup form, secrets, help and live check, and asked for Zoom's Server-to-Server app a second time. - Zoom and Teams provider cards carry an SI-joins status row and a "Set Up SI Joins" action. For the host it opens its usual configuration view; for a provider that does not host the org's meetings it opens the same view in an SI-joins-only mode (no host switch, no switch confirmation). The card body is a CardActionArea, so the two actions never nest. - MeetSiJoinSection ("Let SIs Join Meetings"): the org switch, only the extra fields the join path needs (Zoom Meeting SDK id/secret; Teams ACS endpoint/key), readiness chip + corner ribbon, last join, live check. Zoom's Server-to-Server app is entered once: reused from the Zoom provider when it hosts with one, asked here (Provider Setup's keys and labels) only otherwise. Google Meet's card is gone; the help says Meet joins go by phone. - First-time help for the section in the help panel; Provider Setup help gets an SI-joins bullet. - The SI Meeting Joins tab, its menu entry, MeetSiJoinSettings.tsx and siJoinApi.ts are removed; the client moved into meetProviderApi.ts. ?tab=si-joins lands on ?tab=provider-setup. - Provider Setup's hard-coded greys became theme tokens (dark mode was unreadable), the fallback host email field got an accessible name. - Help-center article rewritten for Settings -> Kamo Meets -> Provider Setup.