Digital Sangam Group • FormFill IndiaFree to use • Local-first • User-controlled
User Guide

FormFill India – step-by-step guide

Use the workflow below for safe, repeatable application assistance.

1. Install

Install the published extension from the Chrome Web Store. For local development or testing, use Chrome's Extensions page and Load unpacked. Confirm that the extension name and developer are FormFill India – Application Assistant and Digital Sangam Group.

2. Complete your profile

Open the Dashboard → Candidate Profile. Enter only information you want to reuse. Save locally. Existing v1.1.0 profile data can be migrated by the current package where present.

3. Quick Fill

Open a compatible application page in the active tab and click Quick Fill Safe Fields. The extension fills only high-confidence matches. Review all critical values afterwards.

4. Deep Scan

Use Deep Scan when Quick Fill does not find enough fields. Review the detected matches and select only the values you want to insert. Dependent dropdowns may require a second pass after the parent field changes.

5. Portal-specific behavior

Some portals need special handling. SSC has a compatibility path for common personal-details fields. RRB retains a Quick Fill compatibility adapter, but dynamic behavior may still require manual completion.

6. Export your data

From the popup or Dashboard Settings, use JSON for a structured backup, Word (DOCX) for a readable document, or Print / Save as PDF for a print-ready copy. Exported files are local and may contain sensitive data.

7. Language and theme

Use the Language selector for supported UI languages. Use the Light/Dark control for display mode. The selected settings are stored locally.

8. Troubleshooting

  1. Confirm the intended application page is active.
  2. Refresh the page and open the form step again.
  3. Try Quick Fill before Deep Scan.
  4. Use the public test form to confirm the extension itself is functioning.
  5. If the page remains unsupported, complete it manually and report the portal/field through Support.
Never send credentials: Support requests should contain only the portal name, field label, non-sensitive error description and redacted screenshots where necessary.