What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.

  • Profile Image

    Allowing people to view their submissions, but not to edit the same

    Asked by yonatann on April 20, 2016 at 08:56 AM


    I wonder whether you have some tips/guidance/reference to the following use case:

    During the period where users fill some form, when some external event occurs (within our own application outside JotForm) we'd like that all users won't be able to edit the entries anymore, but still can see them.

    Any guidance will be appreciated.

    Our current solution to date is to update a hidden field in all forms using the API (isEditable=false) and apply a rule to hide the submit button when isEditable=false. Does this make sense and will prevent the user from saving?

    Thanks in advanced,
    Yonatan Goldberg

  • Profile Image

    Answered by Ben on April 20, 2016 at 10:11 AM

    Unfortunately Yonatan the conditions would not play any role here since the edit submission option does not behave the same as the regular opening of the form.

    What I would suggest here is to actually add a few pages on your form.

    Once you do that, you:

    1. place a welcoming text on the first page

    2. once people go away from the first page to the second, they are no longer shown the back button to return to it (optional)

    3. add a condition that checks if they have filled out some required field or not. If they did, hide the welcome text and show the other text field

    4. the other text field could use {tags} to show values from some of the fields and allow you to show them the important data on that first page.

    5. At this time a condition could hide the next button on the first page as well.

    Doing so will mean that the form can be submitted and that the data would be shown, while they would not be able to edit it.

    Alternatively, you could set up your form and have the submit button on separate page (with captcha or some other field that they would need to fill out - but which you do not wish to show to them). Now as you do, you can simply hide the next button for that page and they would not be able to re-submit their form - meaning that even if they are to change some data, it would not get saved.

    The following guides might be of assistance:

    How to find Field IDs & Names

    How to Create Multi Page Forms

    Do of course let us know if you have any additional questions or if you have any issues and we would be happy to assist with the same.

  • Profile Image

    Answered by yonatann on April 21, 2016 at 08:32 AM


    Thanks for the kind support.

    I'm a bit concerned about the following : "the conditions would not play any role here since the edit submission option does not behave the same as the regular opening of the form".

    We heavily rely on conditions and allows users to edit their submissions (using the URL 
    https://www.jotform.com/edit/{submissionID}). What conditions logic might now work on edit mode? is there any documentation about that?

    I personally succeeded to hide the submit button in edit mode, if you have type the text "456" in the first box the "Send For Approval" button will hide. 

    Thanks again,




  • Profile Image

    Answered by Ben on April 21, 2016 at 10:16 AM

    You are welcome :)

    In regards to conditions, sorry about that Yonatan, you should not have any issues with conditions, they should work properly on edit link just as on the form itself.

    I remembered that there was an issue with the same, but it was resolved shortly afterwards so all should be good :)