Clerk
Query on API Support for Manually Accepting Invitations #2117
-
|
Hello, I'm currently implementing a feature in our application that involves sending invitations to users via Clerk. I've encountered a specific use case and I'm seeking guidance on how to best handle it with Clerk's functionalities. Use Case: Question: Any guidance or alternative suggestions for handling this scenario would be greatly appreciated. Thank you for your assistance. Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
Hey @kamigerami, just to confirm, are u referring to Organization Invitations ? Are you sending invitations from our Backend API or through clerk-js ? Can you provide more information regarding the following sentence ?
|
Beta Was this translation helpful? Give feedback.
-
|
Hello @panteliselef ! Thank you for the quick response. Specifically, I'm using clerkClient.invitations.createInvitation({....}) from @clerk/nextjs/server. Here's the scenario: We have existing users in Clerk who haven't been linked to a company in our database. When another user invites them, they're placed in a "pending" state. However, if these invited users try to sign up using the link sent to them, they're informed that an account already exists and are prompted to sign in instead. After signing in, their status remains "pending" rather than changing to "accepted." We need a way to update the invitation status to "accepted" once these users log in. Is there a way to set the invitation status manually with the api? We are not using the Organization Invitations. |
Beta Was this translation helpful? Give feedback.
-
|
Do you mind sharing if the users sign-in through Account portal, our UI components, or a custom flow of yours ? |
Beta Was this translation helpful? Give feedback.
-
|
They sign-in through the clerk/nextjs |
Beta Was this translation helpful? Give feedback.
-
|
Hello @kamigerami 👋 . Thank you for providing more details for your use case. The invitations feature is intended for inviting new users to your application. It's supposed to be helpful for targeting specific users or enabling invite-only registrations for your application. In general, you wouldn't want to invite an already existing user to your application. I understand that your use case is a bit different though, so let's explore a few options. Would it be ok to revoke the invitation when the user signs in? Revoked invitations don't count as pending. The revoked status might be appropriate after all; the user already exists so there's no point in inviting them again. As an aside, have you checked out our Organizations related features? Sounds like what you call "company" in your application might fit the description of a Clerk organization. You can send invitations for an organization to both existing and new users for your application. Whenever a user joins the organization, the invitation will be marked as "accepted". Hope the above are helpful. Please let us know if you'd like further assistance. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @gkats, yes I believe revoking is a possible fix. Thank you, I will look into it further :) |
Beta Was this translation helpful? Give feedback.
Hello @kamigerami 👋 . Thank you for providing more details for your use case.
The invitations feature is intended for inviting new users to your application. It's supposed to be helpful for targeting specific users or enabling invite-only registrations for your application. In general, you wouldn't want to invite an already existing user to your application.
I understand that your use case is a bit different though, so let's explore a few options.
Would it be ok to revoke the invitation when the user signs in? Revoked invitations don't count as pending. The revoked status might be appropriate after all; the user already exists so there's no point in inviting them again.
As an aside, have …