Manage organizer-supplied access links for tests #56

New issue

Open

opened 2026-11-01 20:12:17 +00:00 by viacheslavshuka · 0 comments

viacheslavshuka commented

2026-11-01 20:12:17 +00:00

Owner

Organizers use existing external meetings and chats. Provide labeled link editing and participant access without provisioning meetings.

Acceptance criteria

Accepted organizers can add, replace, and remove multiple labeled links, including voice/video, chat, and game buttons.
Only confirmed testers and accepted organizers receive link values through Quorum. Pending, tentative, waiting, rejected, and unauthorized users cannot obtain them through API responses.
A published test without links displays a pending-link message to eligible viewers.
Adding or replacing a link emits an update for confirmed testers under their notification preferences.
Organizers may manually reuse the same URL in several tests. The application does not require a particular provider.
Do not add provider credentials, meeting APIs, automatic URL generation, fallback rooms, or self-hosted Jitsi configuration.
Link removal changes Quorum access only. The interface does not claim to revoke copied URLs or external meeting access.
Audit history records the actor, time, and change without placing link secrets in general logs or telemetry.

Validation

Check response filtering for every registration state and a user who loses access after loading a page. Test replacement and duplicate notification-job execution. Assert that provider failures cannot exist as a publication dependency because no provider integration runs.

Dependencies

#44: Create private test drafts and publish complete announcements. Provides published test details.
#52: Register individual testers with approval, tentative status, and capacity checks. Provides confirmed-place eligibility for protected links.

Organizers use existing external meetings and chats. Provide labeled link editing and participant access without provisioning meetings. ## Acceptance criteria - Accepted organizers can add, replace, and remove multiple labeled links, including voice/video, chat, and game buttons. - Only confirmed testers and accepted organizers receive link values through Quorum. Pending, tentative, waiting, rejected, and unauthorized users cannot obtain them through API responses. - A published test without links displays a pending-link message to eligible viewers. - Adding or replacing a link emits an update for confirmed testers under their notification preferences. - Organizers may manually reuse the same URL in several tests. The application does not require a particular provider. - Do not add provider credentials, meeting APIs, automatic URL generation, fallback rooms, or self-hosted Jitsi configuration. - Link removal changes Quorum access only. The interface does not claim to revoke copied URLs or external meeting access. - Audit history records the actor, time, and change without placing link secrets in general logs or telemetry. ## Validation Check response filtering for every registration state and a user who loses access after loading a page. Test replacement and duplicate notification-job execution. Assert that provider failures cannot exist as a publication dependency because no provider integration runs. ## Dependencies - [#44: Create private test drafts and publish complete announcements](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/44). Provides published test details. - [#52: Register individual testers with approval, tentative status, and capacity checks](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/52). Provides confirmed-place eligibility for protected links. ## Related work - [#57: Preserve bookings and prevent stale overwrites when test details change](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/57) - [#51: Schedule another test from a previous test](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/51) - [#22: Keep a durable notification inbox with current action status](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/22) - [#29: Deliver Telegram notifications with bounded retries and current permissions](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/29)

viacheslavshuka referenced this issue

2026-11-01 20:12:27 +00:00

Send timely session reminders and organizer readiness alerts #63

viacheslavshuka referenced this issue

2026-11-01 20:12:31 +00:00

Handle organizer decisions and simple session updates through Telegram #66

viacheslavshuka added the