Skip to content

Commit 0af6421

Browse files
author
James Komara
authored
Update steps for organization ownership transfers
Added additional steps for handling organization ownership transfers.
1 parent c428e71 commit 0af6421

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

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

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

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

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.
271-
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 accessing the current owner's email is not an option, 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
269+
1. The ticket should be assigned ideally to Platform features
270+
2. Ask the user to get the current owner to log in and update ownership.
271+
3. 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.
272+
4. 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.
273+
5. If accessing the current owner's email is not an option, we should have the person requesting access verify their domain ownership by providing a TXT record example for posthog verification.
274+
6. Once verified, membership can be updated for the request.
275+
7. 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
275276

276277
## How should I handle 2FA removal?
277278

0 commit comments

Comments
 (0)