Read and manage submissions

Every response to a form lands in that form's submissions view.

Reading a submission

Open the form and choose Submissions. Each row is one response, in the order it arrived.

Exporting

Three destinations sit in the export well above the list. Export CSV downloads the responses as a file. Export to Data turns them into a sheet in a Data table, one column per question. Export to entities is the one that touches your directory, and it is described below.

Turning a submission into a person

A form is the only place your contacts type their own details, so it is the best thing you have for keeping a directory current. Export to entities carries those answers across.

Choose which responses to import — all of them, or only the ones at a given status — then say which question becomes which field. Email is required: it is how a response finds the person it already belongs to. If a question says what someone is to you ("Program Section", "Runway Category"), map it to Designation and then tell the importer which designation each answer means.

Before anything is written you get counts, not a wall of decisions:

• Filled now — fields that are empty on the person today. These are written.
• Queued for review — answers that disagree with what you already have. Nothing is overwritten; each one becomes an accept-or-dismiss suggestion on that person's profile, and the people list shows a dot beside anyone who has some waiting.
• New people — nobody in your directory uses that address. You can leave them out.
• Needs your decision — a name change, which has no suggestion queue. It happens only if you tick it.

A designation is only ever set on someone who has none, and someone linked to a GIG profile keeps the identity fields they set for themselves.

Afterwards, each response points at the person it belongs to: their name shows on the response, and the import shows on their timeline. Running the same import twice changes nothing the second time.