Three recovery actions on the account Overview. Edit contact updates the owner's email and phone. Password reset generates a one-time sign-in token and returns a URL the operator hands over out of band. Assign/reassign owner searches real logins by email and attaches one as an approved admin.
Also called: I can't log in · wrong email on the account · reset owner password · locked out · change account owner
- 1Edit contact only sends the fields that actually changed, and refuses a no-op.
- 2Password reset returns a copyable one-time URL, defaulting to a 60-minute life, extendable up to 24 hours.
- 3The operator never sees or sets a password — the customer sets their own after the token signs them in.
- 4Every issued token is written to the audit log.
- 5Reassign is available even when an owner is already attached, for the case where the stored owner id is stale or missing after a login-provider cutover.
The reset route spells out the reasoning: 'Plaintext-password handoff between admin and user is a footgun… The user remains in control of their password — admin never sees it,' and 'every issued token is logged to audit_log so a tenant has a defensible record of "who reset our owner's password and when."' The reassign path was added for a real failure: a stale owner id 'left over from a Clerk instance cutover' made Edit-contact and Reset-password fail with NO UI recovery path.
- A stale owner identity made every owner-scoped action fail with no way to fix it from the UI.
- Handing a password between a support agent and a customer is unsafe and unauditable.
- The owner email on file could be wrong with no way to correct it.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →