Docs
Account Ownership and Handover
Account Ownership and Handover
Which accounts move to Impact Hub Houston, in what order, and what each handover needs.
The Principle
Every service the platform runs on is to be owned and billed by Impact Hub Houston, with the build team as collaborators for the support period and then removed. During the build the services ran on accounts the build team held, on free tiers, so nothing waited on account setup and no cost was incurred. The handover is tracked in Linear under IMP-9, with one sub-issue per service.
The Services
| Service | What transfers | What it needs from Impact Hub Houston |
|---|---|---|
| Vercel | The production project (and this docs project) | An owner email and billing authority for a Vercel team |
| GoDaddy | The impacthubos.com registration and DNS | The account the domain moves into, with the email records carried over |
| Supabase | The project, as a transfer between organizations | An owner email |
| Clerk | The application and both instances | An owner email; then the Microsoft and Google credentials are re-homed |
| Resend | The account and the verified domain | An owner email |
| Sentry | The project | An owner email |
| Google Cloud | The project with the OAuth client and consent screen | A Google Workspace admin; then Google verification of the app |
| Microsoft Entra | The app registration for Microsoft sign-in and Outlook | A tenant admin, or the registration is created in their tenant |
| OpenRouter | The account and key for the OS Agent | An owner email with billing |
| Linear | The workspace, with every issue and comment | An admin email; the build team stays as members for the support period |
| GitHub | The repository | A GitHub organization or account to transfer it to |
Order
- Domain first, with the DNS records intact, because everything else answers on it.
- Vercel, Supabase, Clerk, Resend in one sitting, each with a new key rotated into Vercel's environment afterwards.
- Google Cloud and Microsoft Entra, because they change the consent screens members see.
- OpenRouter, Sentry, Linear, GitHub.
Each transfer ends with the old owner removed and the new owner's two-factor sign-in confirmed.
After Handover
- The build team keeps access for the 30-day support period (IMP-48), then is removed.
- Keys the build team ever held are rotated.
- The Clerk webhook endpoint is subscribed to the organization event types (IMP-173).
- Google verification of the OAuth consent screen is requested under the new owner.
APPLICATION_NOTIFY_EMAILSandEMAIL_FROMare confirmed as the addresses Impact Hub Houston wants.
What Does Not Change
The code, the data, the addresses, the members' sign-ins. A well-done handover is invisible to members.