Unauthorized Access: Build-screen instead of publish-screen

  • Profile Image
    Asked on January 24, 2018 at 05:09 AM


    One submitter received the build-screen (see screenshot), with the hidden boxes visible, when he clicked on the form link, and not the right published version - without the hidden boxes?

    How can that happen?

    We use these forms daily, and had never experienced this before.

    Kind regards,



  • Profile Image
    Answered on January 24, 2018 at 09:42 AM

    That page is only accessible if you are logged into your account.

    Its not possible for a user to access that page in any other way.

  • Profile Image
    Answered on January 24, 2018 at 10:38 AM

    Thank you. I know..

    But the hidden boxes was visible when the submitter opened the link?

    (He could see a waiting list note, that wasn't published..and he doesn't have Jotform)

    Have you ever experienced that? (We haven't..)

  • Profile Image
    Answered on January 24, 2018 at 11:57 AM

    Which link did you provide to that user? The form link that you provide on this thread or the build form link that is shown in your screenshot? 

    Even if the user used the build link from the form builder he could not see the form, unless he is logged in to your account. he would be redirected to My Forms page of a guest account. You can test this with the build link from one of my forms. 


    Considering that you have an account you will be redirected to My Forms page in your account when you click on the link I provided. 

    I also checked the login history on your account and all recent logins are from your IP address. 

    How to View Your Account Activity Logs

    Did that user maybe use the same device that you are using or a device that is one of your sub account users is using? 

  • Profile Image
    Answered on January 26, 2018 at 06:45 AM

    Thank you - problem is now solved.

    It turned out, that the submitter had an (really) old browser, that didn't support the hide-function.

    So hopefully it was a one-of-its-kind problem, that won't happen again.

    Thank you.