Solution skill
Clerk org invitations: send, redirect, and accept with the ticket
Complete solution
The invitation email link carries a ticket query param and a status value that tells you which auth flow to run. Build the accept page around the status instead of guessing. Not the full reference manual.
TL;DR: The invitation email link carries a ticket query param and a status value that tells you which auth flow to run. Build the accept page around the status instead of guessing. Confirm the inviter's role before showing an invite form, or the call fails for members. Email must be enabled for the instance (Configure, User and authentication), because Clerk sends the invitation by email.
Clerk organization invitation and acceptance flow
Sending
Only admins can invite by default. Confirm the inviter's role before showing an invite form, or the call fails for members.
Email must be enabled for the instance (Configure, User and authentication), because Clerk sends the invitation by email. If email is off entirely, skip invitations and add existing users directly with the create organization membership backend call, which needs their Clerk user id.
When creating the invitation through the backend API, pass a redirect_url. Without it the invitee lands on the Account Portal sign-in page instead of your app.
Add your accept page to the allowed redirect URLs (Configure, General) or the redirect is refused.
Accepting
The invitee lands on your redirect URL with two query params appended: _clerkticket (the ticket value) and _clerkstatus (the outcome).
sign_up: the user does not exist yet. Build a sign-up flow and pass the ticket into signUp.create so the account is created already attached to the org.
sign_in: the user exists but is not signed in. Pass the ticket into signIn.create with the ticket strategy.
- complete: the user existed and was signed in. Nothing more to do.
Checklist
Test all three statuses, not just the sign-up one. Most teams only test the new-user path and ship a broken flow for existing users.
Revoke stale invitations from the org members page; an old ticket for a departed hire should not linger.
The invited role comes from the invitation, not from the default role. Verify the role on the membership after acceptance, especially if you pre-filled a privileged role.
When to use this
- This covers exactly what the title says: Clerk org invitations.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.
When not to use this
- You are doing a different workflow with Clerk; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.
Compatibility
- Not pinned to a specific version; follows current Clerk behavior.
Evidence
Verified live against the Clerk docs 2026-09-26 at https://clerk.com/docs/guides/development/custom-flows/organizations/manage-organization-invitations. By default only admins can invite, email must be enabled, the accept page receives _clerkticket and _clerkstatus, and the three statuses map to sign-up, sign-in, and complete flows.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_esaVUsWNtwudDTFnlGIk6A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Clerk org invitations: send, redirect, and accept with the ticket <span>— Vectle</span></a>