I'm looking for options to audit and remediate old meet codes in our domain but not having much luck.
Ross Scroggs
Jun 14, 2025, 2:40:55 AM
This is the behavior I've observed, the API only knows about spaces created with the API.
------------------------
I think I have run into the same problem but have some additional observations.
In my case, when I use GAM to interact with Meet, it can only see/access Meet objects which my specific instance of GAM (project/service account) have created via GAM (API). For meets created with the API, it seems to work as expected for any user in the domain when calling from the same GAM instance. It's almost as though the GAM service account is the 'owner' of the meet from the perspective of the API.
Example error from failure of "info meetspace" command:
ERROR: User:
us...@domain.com, Meet Space: spaces/{meet_code}, Show Info Failed: Permission denied on resource MeetingSpace (or it might not exist)
Scenario A: Pre-existing meet code
2. [from my GAM] gam user
us...@domain.com info meetspace spaces/{meet_code_A} -> Failed
3. [from my colleages GAM] gam user
us...@domain.com info meetspace spaces/{meet_code_A} -> Failed
Scenario B: Meet created by MY instance of GAM
1. [from my GAM] gam user
us...@domain.com create meetspace returnidonly > meet_code_B -> Success
2. [from my GAM] gam user
us...@domain.com info meetspace spaces/{meet_code_B} -> Success
3. [from my colleages GAM] gam user
us...@domain.com info meetspace spaces/{meet_code_B} -> Failed
Scenario C: Meet created by a different instance of GAM (my colleagues separate project/service account, same domain)
1. [from my colleagues GAM] gam user
us...@domain.com create meetspace returnidonly > meet_code_C -> Success
2. [from my GAM] gam user
us...@domain.com info meetspace spaces/{meet_code_C} -> Failed
3. [from my colleages GAM] gam user
us...@domain.com info meetspace spaces/{meet_code_C} -> Success
Does this match your experience Ross?
Do you know if it's a bug in the APIs or maybe 'working as designed'?
Is this something we expect Google to fix?