Skip to content

Commit fe89360

Browse files
ja-me-skPostHogeleftheriatrivyzaki
authored
add domain verification when ownership is lost (#14131)
* add domain verification when ownership is lost * Fix typos * Update contents/handbook/engineering/operations/support-hero.md Co-authored-by: eleftheriatrivyzaki <[email protected]> * Update steps for organization ownership transfers Added additional steps for handling organization ownership transfers. --------- Co-authored-by: PostHog <[email protected]> Co-authored-by: eleftheriatrivyzaki <[email protected]>
1 parent bafbf8f commit fe89360

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

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

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -264,12 +264,15 @@ 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:
268-
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.
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 they’re on a paid plan we might need to switch the contact on Stripe.
267+
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:
268+
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
273276

274277
## How should I handle 2FA removal?
275278

0 commit comments

Comments
 (0)