Skip to content

Commit c29c1ce

Browse files
author
James Komara
authored
add domain verification when ownership is lost
1 parent 3fd93e4 commit c29c1ce

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

contents/handbook/engineering/operations/support-hero.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -264,12 +264,14 @@ It's fine to politely direct users to the docs for [self-serve open-source suppo
264264

265265
## How should I handle organization ownership transfers?
266266

267-
In case a user requests for organization permissions to be altered (e.g. the admin left the company) follow these steps:
267+
In case a user requests for organization permissions to be altered (e.g. the only member with owner memebership left the company) follow these steps:
268268

269-
1. Ask them to get the current owner to log in and transfer the ownership.
270-
2. If they have access to the current owner’s email, ask them do a password reset and then login as the owner and perform the action themselves.
269+
1. Ask them to get the current owner to log in and update ownership.
270+
2. If the owner left and they can get access to the current owner’s email, ask them do a password reset and then login as the owner and perform the action themselves.
271271
3. If not, we should email the account owner’s email to see if we get a bounce back. Also check how long it is since they logged in.
272-
4. If they’re on a paid plan we might need to switch the contact on Stripe.
272+
4. While checking the email, we should have the person requesting access verify their domain ownership by providing a TXT record example for posthog verification.
273+
5. Once verified, membership can be updated for the request.
274+
6. Note, if they’re on a paid plan we might also need to switch the contact on Stripe via a separate request to billing @posthog.com
273275

274276
## How should I handle 2FA removal?
275277

0 commit comments

Comments
 (0)