Secure Screening
An access-control layer for issuing private screeners, verifying viewers, and permitting protected video playback.
At a glance
Built
Private screener issuance and viewer verification flows
Handled
Email/password access, OTP visibility, quotas, secure links, and playback permissioning
Result
A controlled screening workflow around protected video playback
The problem
Filmmakers and distributors needed a way to share private screeners without sending generic video links. Each screener needed to be limited to the intended viewer or access method, while still being easy enough for non-technical users to create and open.
The system had to manage issuance, identity checks, access state, playback permissioning, and operational video processing around a third-party protected playback provider.
How it worked
Screener issuance
A creator could generate screeners by email, password, or phone-based access path, depending on the sharing use case.
Viewer verification
The system checked the viewer's screener identity or OTP before allowing playback.
Secure link display
After creation, the product displayed secure URLs, OTPs, and recipient information based on screener type and visibility rules.
Playback permissioning
The app composed the verified screener context with the third-party protected player so access was permitted only after the app-level checks passed.
Operational pipeline
Internal tooling supported screener generation, video upload processing, subtitle attachment, status transitions, cleanup, and stuck-job alerts.
Why it mattered
This gave MovieSaints a controlled workflow for private film sharing: creators could issue targeted screeners, viewers had a clear access path, and playback was gated by app-level authorization before reaching the protected player.
What this shows
This shows how I design secure product workflows where identity, permissions, third-party infrastructure, and operational reliability have to work together.