Accessing Responses
Click the Responses button in the top toolbar to view all submissions for your form. The interface switches from the form builder to the responses view where you can review and manage submissions.
The Responses button displays a count indicator showing how many submissions require your attention. This helps you track new submissions without opening the responses view.
Response States
Form responses exist in two states: Pending and Approved. The state determines whether the submission data appears in your dataset and on maps.
Pending responses await your review and approval. They do not appear in your dataset until you explicitly approve them. Use pending responses to screen submissions for quality, accuracy, or appropriateness before publishing.
Approved responses are published to your dataset immediately. They appear in data tables, on maps, and in any views or analyses that use the connected dataset. Once approved, responses follow your dataset's standard edit and delete permissions.
Auto-Approve Setting
The Auto approve responses toggle in Form Settings controls whether submissions require manual review. This setting fundamentally changes how your form handles incoming data.
When auto-approve is enabled, all submissions are immediately approved and published to your dataset. Respondents' data appears instantly without any review step. This works well for trusted users, internal teams, and low-risk data collection where speed matters more than validation.
When auto-approve is disabled, all submissions enter the Pending state. You must manually review and approve each one before it publishes to your dataset. This provides quality control for public forms, community surveys, and any situation where you need to verify submissions before they become official data.
Toggle this setting in Form Settings by clicking on the form canvas outside individual fields. Find the Auto approve responses option in the Settings section of the right panel.
Reviewing Pending Responses
The Responses view organizes submissions into Pending and Approved sections. Each section is expandable and shows the count of responses in that state.
Click on a pending response to view its details. The interface shows who submitted it, when it was submitted, and all field values they provided. If the form collects geometric data, the location appears on the map in the center panel.
Review each field for accuracy, completeness, and appropriateness. Check that required information is present and formatted correctly. For geographic submissions, verify the location matches the description and falls within expected boundaries.
Approving and Rejecting
Use the checkmark button to approve a response. This immediately publishes the submission to your dataset where it becomes part of your official data. The response moves from the Pending section to the Approved section.
Use the X button to reject a response. This removes the submission from the pending queue without adding it to your dataset. Rejected responses are permanently deleted and cannot be recovered.
The settings icon on each response provides additional options for managing the submission. Use this menu to access advanced actions or make adjustments before approval.
Viewing Responses on the Map
The map in the center panel displays all responses that include geographic data. Pending responses appear differently from approved ones, allowing you to see which submissions still require review.
Click on map features to see their associated response details. This helps you review geographic accuracy and identify duplicate or suspicious submissions based on their locations.
Use the map view to spot patterns in submissions. Clusters of responses in specific areas or linear patterns along routes may indicate coordinated data collection efforts or systematic coverage.
Exiting Responses View
Click the Exit responses button in the top toolbar to return to the form builder. This preserves your work and allows you to switch between managing responses and editing form structure.
Any approved or rejected responses are immediately saved. There is no need to save manually before exiting the responses view.
