Meetings

Skrum is the all-in-one AI project control plane — team chat, tasks and sprints, native video meetings, and inbound code activity in one workspace, with every AI action waiting for a human yes.

Skrum meetings combine scheduling, a private LiveKit room, durable collaboration, and governed follow-up records without depending on Google or Microsoft meeting data.

Find and organize meetings

The Meetings hub has upcoming, past, cancelled, and all views. Search title, agenda, and context; filter by status, date, project, channel, organizer, attendee, RSVP, meeting or webinar format, access, recurrence, recording, transcript, and available artifacts. Every filter, sort, page size, and view is stored in the URL, so a filtered view can be bookmarked or shared with another authorized member. Agenda and calendar views use the same access-aware result set.

Schedule and invite

1. Select Schedule meeting and set the title, agenda, context, start, end, IANA time zone, meeting format, project or channel, and attendee roles.
2. Choose workspace, invited-only, or private access; waiting-room behavior; manual or automatic recording and captions; artifact audience; retention; search opt-in; join window; and up to eight reminders.
3. Add a daily, weekly, or monthly recurrence when needed. A bounded rolling set of occurrences is created with stable occurrence numbers and daylight-saving-safe local time.
4. Edit or cancel only this occurrence, this and following occurrences, or the complete series. Calendar sequence numbers make retries and calendar updates idempotent.

External invite links are reveal-once, hashed in storage, expiring, revocable, and bound to the invited verified email. Guests see a reduced meeting portal rather than workspace data. They can accept, tentatively accept, decline, or later change their response. Revocation removes meeting, realtime, and media access.

Join and collaborate

The lobby checks the configured join window and provides camera, microphone, preview, permission, reconnect, consent, and waiting-room states. Broadcast viewers are not asked for media permission and cannot publish. A recording segment can start only after every current media contributor accepts the versioned notice; a late contributor remains blocked until consent is recorded.

During a meeting, authorized participants can raise hands, react, add manual captions, edit shared notes, draft human-approved action items, vote in polls, and use moderated Q&A. Hosts admit or deny waiting guests. Collaboration is persisted and realtime events contain only a meeting id and revision, causing clients to refetch through the same authorization policy.

Recordings and follow-up

Each recording restart creates a separate segment and private object key. The record page shows attendance, segments, transcript, summary, notes, polls, and actions according to each artifact ACL. Downloads use short-lived private URLs. Transcript and summary search requires both workspace and meeting opt-in. Retention, deletion requests, and legal holds are evaluated per artifact; AI action items remain proposals until a person approves them.

Troubleshooting

• Join is early or late: verify the meeting time zone, start/end time, and configured before/after join window.
• Waiting for admission: an organizer must admit the request; refreshing cannot bypass the durable decision.
• Recording cannot start: verify recording permission, contributor consent, recording-minute capacity, LiveKit egress health, and object storage.
• Transcript is unavailable: check the transcript status, transcription-minute capacity, provider credentials, and postprocess queue before retrying.
• A guest lost access: check invitation expiry, revocation, verified-email match, RSVP, and guest-seat capacity. Do not issue an unscoped replacement token.

See also: Skrum documentation