Skip to main content

Signing Troubleshooting (Cookie Issues)

Written by Thandolwethu Mbatha

Cookies are required for signing documents as they allow QuicklySign to identify and authenticate the signer. This ensures that all actions are accurately tracked in the audit trail for compliance purposes.

If a signer is prompted to register an account when clicking the signing link, it usually means their browser or device does not have cookies enabled.

Instructions

  1. When trying to access a document, make sure cookies are enabled in your browser.

    • Cookies store browser sessions and authenticate your actions in the application.

  2. If you are prompted to login or register unexpectedly, copy the View Document link from the signature request email:

    • Right-click the View Document button and select Copy link address.

    • Paste the link into Google Chrome.

  3. If access still fails, enable cookies in your browser or contact the document owner by replying to the signature request email.

    Visual - Signer Troubleshoot (Cookies-related issue)

    Visual - Signer Troubleshoot (Cookies-related issue)
    ​

Expected Outcome

  • You should be able to access and sign the document without being prompted to login unnecessarily. Signers do not require a QuicklySign Account just to Sign documents

  • Your actions will be tracked in the audit trail to confirm your signature.

FAQs

  • Why do I need cookies to sign a document?
    Cookies authenticate your session so QuicklySign knows who is signing, ensuring the audit trail is accurate.
    ​

  • Which browsers work best?
    Google Chrome is recommended for full functionality and reliability. Other accepted browsers: FireFox, Edge, Safari
    ​

  • What if I cannot enable cookies?
    Contact the document owner to access the document directly.

Contact Support

Should you require any further assistance with this, please contact our Solutions team at Support@quicklysign.com

Did this answer your question?