Provisioning creates or reuses the owner's identity, stamps them admin and approved on the new account, records them as the account's owner, and mints a sign-in token valid for a week. The welcome email sends that link on the tenant's own address.
Also called: magic link · no password needed · welcome email login · first sign in
- 1An existing identity with that email is reused; otherwise one is created.
- 2Account, admin role and approved status are merged onto the identity's metadata.
- 3The account row records the owner's user id.
- 4A sign-in token is created with a seven-day expiry and turned into a link on the tenant's address.
- 5The welcome email states plainly that no password is needed.
Provisioning has to survive whatever the identity provider's instance settings demand, and the code documents that: 'This Clerk instance REQUIRES username + phone_number on create — derive both from the intake data', with a username collision handled by one retry with a short unique suffix, and a clear error when the intake carried no usable phone. Owner recording matters beyond convenience: the account's recorded owner is later what rescues a stranded owner past the approval gate, and it 'is only ever set by the platform-owner-gated assign-owner flow or by provisioning, never by the user, so this can't be self-escalated.'
- A brand-new owner has no credentials and no obvious way in.
- Password-reset flows as a first experience read as a broken handoff.
- Identity-provider signup requirements differ per instance and break naive account creation.
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 →