Automated Lifesize Recording Sharing Review
Every morning, WebRun opens Lifesize, lists the recordings created since the last run with their current sharing permissions, matches each back to its meeting and invitee list in Google Calendar, and posts Microsoft Teams a list of which recordings still need sharing wider and which look too open for what they contain.
How do I check who can view each new meeting recording?
WebRun opens Lifesize every morning, lists the recordings created since the last run with their current sharing permissions, and matches each to its meeting and invitees in Google Calendar. It posts Microsoft Teams the mismatches, so a training session gets shared and a private review stays restricted.
- Yesterday's recordings and their audiences read as one list each morning
- A private review shared too widely is flagged the next day
- Training recordings stuck with one viewer get shared instead of forgotten
Built for IT administrators · operations teams · L&D teams · compliance managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
lifesize.comin a real browser with your saved login - no setup, no API keys. -
1
Lifesize - list recordings and permissions
WebRun opens Lifesize to list recordings and permissions. - Open Lifesize and list the recordings created since the last run
- Capture the title, the date, the length and the meeting it came from
- Read the current sharing permissions on each recording and note which users can view it
- Note recordings still restricted to the person who created them
- Flag anything with no title or owner set, since those get lost fastest
Done when Every new recording has its current audience and permission level captured.
-
2
Google Calendar - match the meeting and invitees
WebRun opens Google Calendar to match the meeting and invitees. - Find the calendar event behind each recording by its date and time
- Read the invitee list and the event title so the intended audience is clear
- Mark recordings from internal training or all-hands sessions as ones that likely need wider sharing
- Mark recordings from interviews, one to ones and private reviews as ones that should stay restricted
Done when Every recording is matched to a meeting and an intended audience.
-
3
Microsoft Teams - post the sharing decisions
WebRun opens Microsoft Teams to post the sharing decisions. - Post the admin channel a list of yesterday's recordings with their current audience beside the intended one
- Put the mismatches first: private sessions shared broadly, and training sessions still visible to one person
- Show the participants from the calendar event so the right audience is obvious
- Leave every permission change to the admin. WebRun does not change sharing settings
Done when The admin has yesterday's recordings and their sharing decisions in Microsoft Teams.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it share or restrict a recording on its own?
No. WebRun reads the current permissions and reports the mismatches. It never changes a sharing setting, never sends a recording link to anyone, and never deletes a recording. Every change stays an admin click.
Does it watch or transcribe the recordings?
No. It reads the recording title, date, length and permissions, plus the calendar event behind it. The video itself is never opened, downloaded or transcribed.
How does it know who the recording was meant for?
From the matching Google Calendar event: the title and the invitee list. A training session with twenty invitees and a two-person review get different intended audiences, and the mismatch is what gets flagged.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.