I am attempting to create a form link for our full time student registration that cannot be shared amongst students and families as sharing the link and registering for classes is the last step in a fairly entensive enrollment process. Is there a way to either make the link to the form a one time use only link or a link that cannot be forwarded to other students? Thank you thank you for any help you can provide!
Hi Dan, there are several ways to achieve this. It mainly depends if you have them filling out that form behind a login or not. If you share a bit more context regarding what the steps are prior to getting to the page where you have that form, we could help more. Easiest way would be to upload the list of students so that you get a u ique record for each one. Then you wpuld create a form view, append that record ID and then send it via email. In order to only be used once, you can create a simple rule on the view that if X has a date or data ot anything, it hides the form view. That way once the form has been filled, that link would no longer display a form.
Currently our students apply to our school and then receive an email that includes a link to the form that is not protected by a login as we do not have a list of the current students as this is always changing through the enrollment window. We believe that our students and families are sharing this email which is allowing some students to bypass the initial application and move straight to requesting courses. Unfortunately, the initial application step occurs through a different system that I do not have any ability to control. Thanks for problem solving with me!
I see. Unfortunately, in your current setup, there isn’t a way to make the link single-use since it’s sent through a system you don’t control. Any solution to send unique links would need to be associated with a specific record in Knack.
If you could get the data from the other system—such as new registrations—sent over to Knack, you could create a new record and then send the link associated with that record. This would solve your issue. I understand you don’t control the other system, but you might have the other system BCC a mailhook you control. This could then trigger automated steps to create a Knack record, get the unique link, and email the link to the parent.
This approach would require using Make or Zapier along with Knack.