The lead or student cannot sign a workflow

This article outlines common device-specific and browser-specific considerations to help troubleshoot issues quickly.

Device and Browser Compatibility for Workflow Completion

The device type and internet browser a lead or student uses can significantly affect their ability to complete required steps within the workflow—especially tasks like form submission, document review, and electronic signature. This article outlines common device-specific and browser-specific considerations to help troubleshoot issues quickly.


iPhone Users

Safari Browser

Safari is the default browser on all iPhones and generally works well; however, users may encounter issues specifically with document signing or PDF interactions.

Common Issues:

  • PDFs fail to load or open in a signable format

  • Signature tools do not appear

  • Page does not refresh after signing

Troubleshooting Steps:

  1. Start with simple fixes:

    • Reload/refresh the page

    • Close and reopen Safari

    • Clear Safari cache and cookies

  2. Review Safari Settings:
    Adjusting a few privacy settings can quickly resolve most signing problems.

    • Disable Browser Extensions (if any are enabled)

    • Turn Off “Prevent Cross-Site Tracking”

      • Settings → Safari → Privacy & Security → Prevent Cross-Site Tracking (toggle off)

    • Ensure “Block All Cookies” Is Off

      • Settings → Safari → Block All Cookies (toggle off)

These settings ensure that embedded signing tools and authentication steps can function properly within the workflow.


Chrome Browser

Chrome on iPhone is convenient, but it does not support native PDF signing because it lacks built-in PDF editing or markup capabilities.

Important Notes:

  • Users cannot electronically sign PDFs directly inside Chrome on iOS

  • Signature fields may appear but will not function normally

  • PDFs may download without the ability to complete required steps

Recommended Workarounds:

  • Use iPhone’s native Markup tool (via the Files app or Safari preview)

  • Use a third-party PDF app such as Adobe Acrobat Mobile

  • Access the workflow through Safari instead of Chrome if signing is required


Android Users

Android devices generally experience no known issues when completing workflow tasks—whether signing documents, uploading attachments, or submitting forms.

Most Android browsers (Chrome, Samsung Internet, Firefox) allow PDFs to open with built-in signing options or route them to apps that support digital signatures.


Summary of Best Practices

  • If a user on an iPhone reports signing issues, first confirm which browser they are using.

  • Safari usually works with minor adjustments to privacy settings.

  • Chrome on iPhone does not support in-browser PDF signing—redirect users to Safari or a PDF-signing app.

  • Android devices typically work with no additional troubleshooting needed.