Playbook, SaaS company
Nobody still at the company can administer the account
Access on a team product is not something you grant. An administrator inside the customer's own company adds people, removes them and decides what each can do, and your side of it is mostly a role somebody forgot to hand over. The bad version of this is a workspace whose only owner has left, where everybody still using it can work and nobody can change anything.
Why this is not the general answer
The handling pattern for account access problems holds across every trade. What follows is the part that does not.
- Permission is delegated to the customer, so the person who can let somebody in is a colleague rather than anybody on your side, and an answer that does not say so sends people to the wrong place entirely.
- The orphaned workspace is the hard case: the sole owner has gone, the remaining members hold no administrative rights, and resolving it is an identity question with proof attached rather than a support ticket.
- An invitation is a different object from an account, so somebody saying they cannot get in may be holding an expired invite, or one sent to an address they never read, and neither looks like a sign in problem to them.
- Handing access to whoever asks is precisely the failure this trade has to guard against, so the refusal here is protecting the customer's data rather than protecting you.
How it arrives
- our admin has left and no one can add users
- my invite link has expired
- i can see the workspace but cannot change anything
- how do we get ownership transferred to someone else
- i was removed from the workspace by mistake
- can you add me to my company's account
What has to be indexed for this to work
| The ownership transfer procedure, including what proof you require | Who may request it, what evidence of authority you ask for, and how long it takes. This is the single most valuable document in this pair, it is asked for by a company in a genuine bind, and it is almost always unwritten. |
|---|---|
| The role table, in the product's own wording | Every role, what each can and cannot do, and which of them can invite, remove or change billing. Most of I cannot change anything is not a fault, it is a role, and a published table ends the conversation in one reply. |
| How invitations behave | How long an invite stays valid, whether it is tied to the exact address it was sent to, who can resend it, and what happens if somebody accepts on a different email. Expired invitations produce a steady stream of messages that read like sign in failures. |
| What happens to a removed member's work | Whether their content stays in the workspace, whether it is reassigned, and whether the seat is freed straight away or at renewal. Somebody removed by mistake is asking about their work, not about their login. |
The reply
Who can add, remove or promote people is set by the role you hold in the workspace, and the table of roles is on the permissions page [1]. If the only owner has left the company, the account is not stuck, but transferring ownership is a request the team handles with proof of authority rather than something done from a chat window, and what is required is set out there [2]. I cannot see your workspace, confirm who administers it, or change anybody's access. Leave your name, your work email and the workspace name, and the team will pick it up.
It separates the two cases in the first two sentences, because one is answered by a document and the other by a procedure. Saying the account is not stuck matters, since the person writing usually fears the data is gone with the person who left. It then refuses three specific things, including naming the administrator, which is the one somebody will try next.
Where it stops
The trigger. The visitor asks to be added to a workspace, to have rights changed, to have ownership moved, or asks who the current administrator is.
Access is granted by an administrator on your side or, where there is not one left, through a transfer request the team handles with proof of authority. I cannot do either. Leave your name, your work email and the workspace name and it will go across today.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never name, confirm or hint at who owns or administers a workspace, whoever is asking and however plausible the reason.
- Never say access has been granted, restored or removed, since nothing here writes to any account.
- Never confirm whether a named person is a member of a workspace.
- Never suggest opening a second workspace as a way round a locked one, because it splits the data and creates a second subscription.
Questions
- Somebody insists they own the account. Should it soften the refusal?
- No. The wording should stay identical whether the claim is convincing or not, because a refusal that bends under pressure is a refusal that can be talked past. Route it fast instead, so a person who can actually check authority sees it quickly.
- Can it resend an invitation?
- No. It cannot send anything or write into a workspace. It can explain how long invites last, who can resend one, and why accepting on a different address does not work, which covers most of these without anybody needing to intervene.
- Is the orphaned owner case worth documenting publicly?
- Yes, and it is worth documenting before it happens to somebody. The companies asking are usually in the middle of a departure they did not plan for, and a published procedure with a list of what to send turns a frightening week into a form.
Keep reading
- Everything for a SaaS companyOne widget serves prospects, trialists and paying customers. What it can answer about plans and limits, and what has to reach a person.
- Handling account access problems in generalLocked out, wrong email, a colleague who left, no admin remaining. Identity cannot be checked in a widget, so explain, collect, hand over.
- Three different people send this message and only one of them owns the dataDeactivating a member is not deleting them. Backups, subprocessors and who is asking decide the answer, and none of it happens in chat.
- The one question where the correct reply is somewhere elseAn assistant reads documents, not systems, so it cannot know the service is degraded. Point at the status page and say nothing about now.
- The account is open and nothing has been set up yetImport limits, what an admin configures first and what trial work does at conversion. Onboarding answers that stop a week one stall.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.