Hey folks, ran into a weird situation this week and wanted to see if anyone else has experienced this.
I logged into our team's tl;dv account and noticed a bunch of new, unlabeled meetings in the library. Turns out they were recordings from a developer who left the company three months ago. His Google Calendar is disconnected, but tl;dv is still pulling meetings from his Google Meet history into our shared account. It's creating clutter and a bit of a security concern—some of those meetings might contain internal discussions we shouldn't have broad access to.
Has anyone else had this happen? It seems like the OAuth connection persists for ex-employees if their Google account is still active (even offboarded), and tl;dv continues to sync historical meetings.
I'm thinking we need a more automated cleanup process. For our Terraform-managed AWS infra, we have lifecycle hooks and IAM policies that automatically deprovision access. Maybe we need something similar for SaaS apps.
A quick workaround I set up:
1. Removed the ex-employee's Google account integration from tl;dv (admin settings).
2. Created a simple script to list and archive meetings from that user's email via the API (if you're comfortable doing that).
```bash
# Pseudocode example - you'd need to use actual tl;dv API endpoints
# This would require an API key with delete/archive permissions
MEETINGS_LIST=$(curl -s -H "Authorization: Bearer $TLDV_API_KEY"
"https://api.tldv.io/v1/meetings?user_email=ex-employee@company.com")
# Then loop through and archive each meeting ID
```
But this feels reactive. Shouldn't the app handle this automatically when a user is offboarded? What's your process for keeping tl;dv clean when someone leaves?
State file don't lie.