Skip to content

Meetings

Coordination available; live media in progress

Katra meetings keep preparation, participation, decisions, and follow-up attached to a Channel or Direct Message.

  • One-time scheduled meetings with desired outcome and structured agenda items
  • One shared live-room lifecycle per Channel or Direct Message
  • Organizer start, end, cancellation, participant join, and participant leave transitions
  • Participant-private attendance and room presence
  • Participant-private notes, decisions, and assigned action items
  • Durable meeting chat and semantic message reactions
  • Transient room-wide reaction cues
  • Participant-private iCalendar export
  • Copied-link guest lobbies with expiry, throttling, revocation, and a 25-guest cap
  • Email-bound meeting invitations with individual revocation
  • Participant removal that revokes active meeting authority and meeting-only guest sessions

Self-hosted LiveKit transports ephemeral audio, video, and screen-share tracks. Katra Server remains authoritative for room access and issues short-lived exact-room credentials.

Real media is still in progress. Independent-browser reconnect, trusted TLS, direct UDP, and TURN fallback must be proven before the meeting surface is considered ready for a shared installation.

Recording, transcription, consent, storage, retention, and durable media artifacts remain explicit future boundaries. No recording capability should be inferred from the current meeting controls or design scaffolding.

  • Recurring meetings and per-instance editing
  • Background push while Katra Client is closed
  • Quiet hours and broader notification delivery
  • Manual waiting-room behavior beyond the current guest admission path