Skip to main content

Sharing, invitations, and chat history

Choose invitations for access tied to named accounts, or a share link when anyone holding the URL may use the course without signing in. Both let learners watch course videos and use Q&A. Their questions use the course owner's AI answer allowance, and the owner can read and export the saved conversations.

An invitation must be accepted while signed in to an account whose verified email matches the recipient. Sending an invitation alone does not grant membership. A share link can be forwarded; it is not limited to the people the owner originally sent it to.

Permissions by access route​

This table covers ordinary course access through the app and its API. “Participant” means an account that has accepted an invitation. A person can have both membership and a share link; the route used for each request matters.

OperationCourse ownerInvited participantShare-link user
Open the course and play its videosYes, signed inYes, signed inYes, with the current link; login is optional
Ask Q&A questionsYesYesYes
Edit/delete the course, change its videos or their orderYesNoNo
Edit the source video or transcriptVideo owner onlyNo permission granted by membershipNo permission granted by the link
Manage invitations, participants, and the share linkYesNoNo
Read saved course chat history, including other people's questionsYesNoNo
Export course chat history as CSV or delete itYesNoNo
Leave an invited courseRemove a participant through member managementYes, leave their own membershipNo membership to leave

Playback access applies to videos in the course. It does not grant access to the owner's whole video library or the source video's editing screen.

Opening a share link while signed in still uses that link's course scope. An invalid link or a video outside that course does not fall back to your account's private video access.

Participants and link users can see answers in their current chat panel, but cannot load saved course history or export even just their own past questions through the history API. The owner-only history includes Q&A exchanges. Visible messages and saved chat logs are different data.

Example: teacher A and learner B​

Teacher A owns a course. Learner B accepts an invitation and asks from the signed-in course page:

  1. The API checks B's access and reserves one response from A's AI answer allowance before answering. B's own allowance is not charged.
  2. A can read the saved question and answer in History, export them as CSV, and see B's user ID, username, and email address as the questioner. Other participants cannot retrieve those logs.
  3. If B instead uses the public share URL, the allowance is still A's, but the log is marked as shared-origin and its questioner fields are empty in history and CSV—even if B is signed in. It does not identify which link visitor asked. Information B puts in the question text is still saved and visible to A.

The allowance is shared across requests charged to A's account, not allocated separately per learner or course. At A's AI answer limit, new Q&A requests charged to A are refused, including requests from A, invited participants, and link users. If A's account is blocked for excess storage, these chat requests are also refused. These checks do not themselves revoke membership or prevent opening the course and playing available videos.

The API reserves usage before generation and attempts to return the reservation when it cannot complete the answer. Reading a course or an existing answer does not reserve another AI answer. Separate rate limits can temporarily reject requests even when the owner still has allowance. See the quota repository and chat request handling.

Removing access and keeping history​

Owner actionWhat stops workingWhat remains
Revoke a pending invitationThat invitation can no longer be acceptedOther memberships and the share link; existing chat history
Remove an accepted participantNew course reads and chat requests through that membershipA valid public link can still be used; previous questions remain in owner history/CSV
Disable the share linkNew course reads and chat requests using that linkOwner and invited-member access; previous shared-origin questions
Save a different share-link slugThe old URL no longer matches this courseThe new URL works; memberships and history remain
Delete course chat historySaved questions, answers, feedback, and their evaluations are deletedCourse access and membership

Revoking an invitation applies to a pending invitation. After acceptance, remove the participant instead. Removing membership does not revoke a separate share link, and disabling a link does not remove participants. To stop both routes for someone who knows the link, remove their membership and disable or change the link as appropriate.

Access changes are checked on new requests. They do not recall copies, exported CSVs, or messages already displayed, and an already-authorized response may finish. Issued video playback URLs may remain usable: S3-compatible playback URLs are signed for one hour from issuance, and external video URLs have their own access rules. Changing the share slug does not permanently reserve the old slug; reusing it can make that URL work again. See media URL handling.

Removing a participant or disabling a link does not delete chat logs. To remove saved conversations, the owner uses the separate course chat-history deletion action. This removes the whole course history, not just one participant's questions, and does not erase exported copies.

Choose, share, and verify​

  1. Open a course you own. Check its included videos and explain to learners that you can read their questions and answers.
  2. For named participants, open Manage members, enter their email addresses, and send invitations. The recipient opens the email link, signs in with the matching verified email, and chooses Accept and join. Check the member list. For public access, open Share, save a share slug, then copy the URL.
  3. Verify with a separate learner account or a signed-out browser, according to the chosen route. Check playback and chat, and the absence of course-editing and saved-history controls. A new Q&A response uses the owner's allowance.
  4. As the owner, open History and export CSV if needed. Invited participants' questions have questioner details; link questions are marked as shared-origin. Use test questions suitable for the owner to read.
  5. Test revocation through the same route: remove the participant or disable the link, then reload and make a new request. An already-open video or chat panel does not prove access is still authorized. Check the table above if a second route remains.

Implementation references​

ResponsibilitySource
Owner/member course reads, public link reads, owner-only edits and link changescourse-repository.ts
Verified-email acceptance, invitation revocation, member removalcourse-invitation-repository.ts
Chat access, allowance owner, actor, and persistencemessage-service.ts
Owner-only history/CSV and shared-origin questioner fieldschat-repository.ts

Related: Authentication and access control, Videos, courses, and scenes.