example handover / ACCOUNTS.md
ACCOUNTS — Job Board, Granite State Mechanical
This is an example from the demonstration project on this site, with a fictional company and redacted secrets. The point of this file: every account is owned by you, inventoried in one place, with nothing of yours registered under the developer's name. For a real build, this is the page you'd check the day we shake hands — and the day you decide to lock me out.
The inventory
| What | Where | Owner (account holder) | Login email | Password / key |
|---|---|---|---|---|
| Domain name | (registrar) | Granite State Mech. | office@gsm.example | ████ redacted |
| DNS | (DNS provider) | Granite State Mech. | office@gsm.example | ████ redacted |
| Hosting | (static host, free tier) | Granite State Mech. | office@gsm.example | ████ redacted |
| Source code | (code host, private) | Granite State Mech. | office@gsm.example | ████ redacted |
| (mail provider) | Granite State Mech. | office@gsm.example | ████ redacted |
Who can touch what
- You hold the owner login for every row above.
- Addison has collaborator access to the source code and hosting — access you can revoke in two clicks, and this file tells you where those clicks are.
- Nothing renews against my card. Every renewal (domain, ~yearly) bills to the card on file in your registrar account, and the renewal dates are in your calendar (set up at handover).
If you ever change developers
Revoke my collaborator access (rows above), change the passwords, done. Nothing else to untangle — that's what this file is for.