Skip to content

πŸ“(docs) design spec: recording delegate β€” alternative to #794#1189

Open
mmaudet wants to merge 1 commit intomainfrom
docs/recording-delegate-design
Open

πŸ“(docs) design spec: recording delegate β€” alternative to #794#1189
mmaudet wants to merge 1 commit intomainfrom
docs/recording-delegate-design

Conversation

@mmaudet
Copy link
Copy Markdown
Collaborator

@mmaudet mmaudet commented Mar 20, 2026

Context

PR #794 proposes adding configurable recording permissions with two levels: admin_owner and authenticated (any logged-in user can start/stop recordings). While this addresses a real need, @lebaudantoine raised concerns about multi-tenant deployments where authenticated users may belong to different organizations.

This spec proposes an alternative approach that solves the same problem β€” "the meeting organizer is absent and no one can start the recording" β€” with more granular control.

Proposal: Recording Delegate

Instead of opening recording rights to all authenticated users, this design introduces a lightweight per-user delegation system:

  • Admins/owners can grant recording-specific rights to individual users (before or during a meeting)
  • Participants can request recording rights β€” admins approve/reject in real-time
  • Auto-approval when no admin is present: if an authenticated user requests recording rights and no admin/owner is in the room, the request is auto-approved after 30 seconds
  • Session or permanent: the admin chooses whether the delegation lasts for the current meeting only or persists

Key differences with #794

#794 This proposal
Granularity All authenticated users Per-user delegation
Control Global setting or per-room config Admin grants/revokes individually
Multi-tenant safe No (all auth users get access) Yes (explicit delegation)
Absent organizer Solved (all auth users can record) Solved (auto-approve after 30s)
Complexity Lower Higher

Status

This is a design spec for discussion only β€” no code changes. The spec needs review and alignment from maintainers before any implementation begins.

The full spec is in docs/superpowers/specs/2026-03-20-recording-delegate-design.md.

Related

/cc @lebaudantoine @gigi206

Design spec for a lightweight recording delegation system as an
alternative approach to PR #794's global permission model.
Instead of opening recording rights to all authenticated users,
this proposes granular per-user delegation with request/approve
flow and auto-approval when no admin is present.
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant