Online application form with individual login ID

  • Profile Image
    Asked on January 17, 2018 at 08:58 AM

    Can we create online application form with having user login ID for each applicant. So that applicant can login and register website with form anytime and able to edit or upload the documents.

  • Profile Image
    Answered on January 17, 2018 at 10:49 AM

    Please note that login forms are not allowed. It is also against our Terms of Use to collect any type of login credentials. 

    If you want to protect your online form, you can use a text box field (name it access code or similar) and conditional logic to hide all other fields if the 'code' is not correct. 

    How to Show or Hide Fields Base on User's Answer

    Here is my demo form: 

    Access code - 12345

    Feel free to test it. 

    You can create a different 'Access Code' for each of your users. 

    Inside of this guide, you can find how to allow your users to edit their submissions:

    How to Let Users Update Their Form Submissions at a Later Date

  • Profile Image
    Answered on January 17, 2018 at 04:15 PM

    Joanna -

    I've been trying to identify a definitive "safe" process for accomplishing this type of password work-around. I get that you and your colleagues are hesitant to advise us on procedures that might violate JotForm's Terms of Use. However, this topic is clearly a hole that needs to be addressed by JotForm, or you and your staff wouldn't be providing these kinds of tips.

    I've read varying work-around solutions from your colleagues. (See Ashwin's reply suggesting that passwords be emailed to users, but not used of forms. How does that work?!?; and see David's technique for using an accordion style collapse-field technique

    So, I'm confused and still unclear about these three points:

    1.  What specific field names (labels) can be used without our forms being auto-disabled? You suggested using "access code", as opposed to "password". I've also read different opinions about the use of the words "keyword", and security code". Are there other safe word combinations we can use that won't flag your filters?

    2.  Is your demo the only way to "safely" go about this, or the best way? Or, is it just one way you selected for the purposes of this thread? Are there other "approved" methods?

    3.  What would you consider a safe strategy for implementing "access code" fields (beyond the mere setup for conditional logic), and how would we structure that as a process?

    - Thanks for your insight

  • Profile Image
    Answered on January 17, 2018 at 05:14 PM

    We'll answer your questions on a separate thread here