Get started
Forms

Forms

Build a form or survey at forms.syncgaze.in, share a link, and collect responses. Good for sign-ups, feedback, orders, and quizzes.

Build a form

Click New form, give it a title, and add questions. Each question is a field — pick the type that fits the answer:

  • Text / paragraph — short or long written answers.
  • Email, phone, number, URL, date, time — validated for the right format.
  • Multiple choice, checkboxes, dropdown — pick one or several options.
  • Rating & scale — stars or a 1–10 scale.
  • File upload and signature — collect documents or a signed agreement.

Mark any field required so it must be answered before submitting.

Settings

Tune how the form behaves:

  • Custom submit button text and a thank-you message or redirect URL.
  • Collect respondent email, and optionally limit to one response per email.
  • Allow people to edit a previous response.
  • Show a progress bar, shuffle fields, and set open/close dates.

Quiz mode

Turn on quiz mode to mark correct answers and assign points. Respondents can see their score, and you get the results per person — handy for tests and assessments.

Share & collect

Publish the form and share its public link — anyone with the link can respond (no SyncGaze account needed). Responses collect in the form's Responses tab, where you can view them, see a summary, and export them for a spreadsheet.

Public by linkThe response page is open to anyone with the link; you don't need to invite people. Only you (and anyone you share the form with) can see the collected responses.

Troubleshooting

ProblemCauseFix
People can't open the formIt isn't published, or it's past its close date.Publish the form and check the open/close dates.
Someone submitted twice“One response per email” is off.Enable it and require the respondent's email.
Quiz scores look wrongCorrect answers/points weren't set on every question.Open each quiz field and set the correct answer and its points.
{# Help Assistant is self-injected by static/help/assistant.js (loaded in base.html). Nothing to render here — kept so the base.html include stays valid. #}