Skip to content
Notifications
Clear all

Help: I'm locked out of my You.com workspace after a teammate left the company.

1 Posts
1 Users
0 Reactions
5 Views
(@sre_mom)
Eminent Member
Joined: 3 months ago
Posts: 18
Topic starter   [#804]

Hi everyone. I'm hoping to tap into the collective wisdom here regarding a workspace access issue on You.com that's become a critical blocker for my team.

Here's the situation: We've been using a You.com Pro workspace for a few months to centralize our AI-assisted research and development workflows. The workspace owner was a senior engineer who recently left the company. Unfortunately, the offboarding process was rushed, and ownership of the workspace was never transferred. Now, none of the remaining team members have admin-level access. We can't invite new members, adjust billing, or change workspace settings. It's effectively a single point of failure that we didn't anticipate.

I've already attempted the obvious paths:
* Contacting our former colleague directly (they are cooperative, but they no longer have access to their company email and You.com's system won't let them transfer ownership from their personal account).
* Submitting support tickets through the You.com help center (the response has been slow, and they are asking for proof of domain ownership and original billing details, which we're gathering).
* Trying to find any administrative API endpoints or CLI tools (the documentation seems limited for workspace administration).

This feels like a classic incident response scenario where our "blast radius" is limited but our "remediation time" is growing. Has anyone else navigated a similar administrative lockout with You.com? Specifically:

* Is there a verified escalation path for workspace recovery that you've used successfully?
* Does You.com support have a process for verifying company control via domain or VAT numbers when the original owner is unavailable?
* From a preventative SLO perspective, how are others structuring workspace ownership to avoid this? (e.g., using a shared "team" email as the owner, regular ownership reviews?)

I'm also drafting a runbook for our internal docs to prevent this in the future, so any insights into your administrative safeguards would be incredibly helpful. I'll be sure to share the postmortem once we get this resolved, as I'm sure others could benefit from the steps we took.

Thanks in advance for any guidance you can provide.


pagerduty certified lifer


   
Quote