Sharing Recordings

Detego lets you share any saved recording by generating a unique share link. The recipient can view the recording without needing a Detego account.

The sharing flow:

1. You generate a share link — from a saved recording, Detego calls the share API with the recording ID (and optionally an analysis ID)
2. A share token is created — the server generates a cryptographically random token and stores it in the shared_links table alongside the recording reference, your user ID, and an expiry timestamp
3. You send the link — the share URL follows the pattern /shared/<token>. Copy it and send it to your colleague via email, chat, or any other channel
4. The recipient opens the link — the shared page loads the recording data using the token, with no sign-in required

When someone opens a shared link, they see a dedicated read-only page that displays:

• Recording identity — the share token and a reference back to Detego
• Recording metadata — station name, device ID, and file information from the original COMTRADE data
• Analyzed with Detego attribution — a badge indicating the recording was analyzed on the platform

The shared view is designed as a lightweight, self-contained page. It renders as a server component for fast initial load and SEO — no client-side JavaScript is needed to display the core content.

Share links are designed to be secure by default:

• Token-based access — each link contains a unique, randomly generated token. Only someone who has the token can view the recording. Tokens are not guessable or enumerable
• No sign-in required — recipients do not need a Detego account to view a shared recording. This makes it easy to share with external stakeholders, contractors, or equipment vendors
• Owner verification — only the recording owner can create share links. The API verifies ownership through Supabase Row Level Security before generating a token
• Authentication required to share — you must be signed in to generate a share link. Unauthenticated requests are rejected with a 401 error
• Input validation — the share API validates all inputs with Zod schemas, ensuring only valid UUIDs are accepted for recording and analysis IDs

Share links expire automatically after 30 days from the date they are created. After expiration, the link will no longer work and the recipient will not be able to access the recording.

If you need to share a recording again after a link has expired, simply generate a new share link. Each generation creates a fresh token with a new 30-day window.

Shared views are intentionally limited compared to the full viewer experience:

The shared view is a snapshot — it shows what was available at the time the link was created. If you re-analyze the recording or add new computed signals after sharing, the shared link will not automatically reflect those changes unless you generate a new link with the updated analysis ID.