-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update email action to invite users who don't have accounts #1002
Comments
Let's discuss. Could also see accomplishing this by creating users via API or even action — maybe having a special function that can take an email field and either creates a new user from that field (and sets a member field to that user) or, if the user already exists, sets a member field to that user? |
Another thought: can we solve this to some degree by implementing public forms? That is, a form that prompts a user to login or create an account, and then once they've done so, allows them to submit it? We need this for ICOR as well. |
@tefkah we need your thoughts on this one -- the context is in the motivation. Basically, we want to be able to accept a discussion pub from someone with only an email address, but then give them the ability to see/edit the pub they created, and in this case, to trigger a workflow that sends them a form to verify the discussion. |
Another use-case for this popped up: ICOR wants to have a public form, and wants users to be able to save draft forms before they submit them. Yes, we should probably implement some kind of local auto-save, but a "native" PubPub way to do this would be to create a "save draft" button that creates the Pub and puts it in a draft stage, and allows the user to visit it again. In this case, it would also trigger an email to the user with an invite to the pub. The problem we're facing in all of these cases is simply how to associate an email address to a user — either one that already exists, or by creating a new one. In the invited review case, the admins are responsible for creating the user, if they don't exist. But we need some way for "public" users to be able to do this, too. For these cases, I'm increasingly leaning towards relying on existing mechanisms. For implementing public forms for the ICOR case, we could simply require a user create an account to fill them out, and then add them as a pub contributor. For invitations, we could update the email action's invitation flow to process email fields such that it either adds the user as a Pub contributor member if it exists, or automatically creates an invitation and adds them if it doesn't. |
Motivation
So an admin can send emails with forms to people who create discussions and thus are not (yet) members. In this case, it's to create a discussion verification flow for users where we're collecting email addresses on the front-end and want to create memberships for them as part of that flow.
The other cool thing this does is essentially allows you to create custom magic link flows for different workflows (via API or otherwise). E.g., you can have someone:
Requirements
Acceptance Criteria
redirectTo=
parameter that redirects to the form with pub IDExtra work
The text was updated successfully, but these errors were encountered: