Create custom columns with submission tags

Surface the field values that matter as their own columns on the Submissions page, so you can scan, sort, search, and scope submissions by the data inside them.

How submission tags work

A submission tag pulls a value out of each submission and labels the submission with it. Tags are defined in the form's code, in the Tags area of the Code Editor (the tagExpressions block).

Once a tag is in place, it does three things for you:

• Custom columns › each tag becomes its own column on the Submissions page, so key data is visible at a glance instead of buried inside the form.

• Searchable values › the tagged value is searchable, making submissions easier to find.

• Access control › because the value is attached to the submission, you can write permission conditions that show a role only the submissions whose tag matches.

Define a tag

Each tag is one line in the Tags area: a column header (the key) paired with an expression that produces the value (most often a component ID). For example, to add a "school" column driven by a schoolLocation dropdown:

{ "school": "schoolLocation" }

To find the component ID, go to the form builder to edit your form. Click on the component you want to use, then scroll down in the properties side bar to find the ID.

Add more tags by listing more key/value pairs:

{
  "school": "schoolLocation",
  "grade": "gradeLevel",
  "status": "requestStatus"
}

Build richer values with expressions

A tag value can be any expression, not just a single component ID, so a column can combine or transform fields. These use the same expression language as formulas and computed fields.

Combine two fields with a template literal: This combines two values. If schoolLocation is Lincoln Elementary and schoolYear is 2026-27, the column shows "Lincoln Elementary 2026-27."

{ "School And Year": "`${schoolLocation} ${schoolYear}`" }
{ "Candidate Name": "`${candidateFirstName} ${candidateLastName}`" }

Return a value conditionally: This is an "if / then / otherwise" statement. If foodAllergy is true (checked, filled in, or true), the column shows "Yes"; if it's empty or false, it shows "No."

{ "mealModification": "foodAllergy ? 'Yes' : 'No'" }

Use a helper function (see the full helper list): This returns the unique ID of the current submission, not a value from a form on the field.

{ "submissionId": "getSubmissionId()" }

See your columns on the Submissions page

After adding a tag, publish the form, then submit or wait for a submission that carries the value. The column will not show until there is data to fill it.

Once the column is there, you can put it to work from the Submissions page.

• Sort by clicking the column header (click again to reverse).

• Filter by the custom column from the Filters menu in the toolbar.

• Search the tagged value from the search box in the toolbar.

• Save the setup as a view › once you have the filters, search text, and sort order you want, save them as a named view so you can come back to it without rebuilding it.

Scope who sees which submissions

The same tags that create your columns can limit what each role sees. Pair a submission tag with an account tag and a "Tag Matches Account Tag" condition, and a user sees only the submissions that belong to their group (for example, a principal seeing only their own school). The full walkthrough is in Scope submissions by tag.