Field Types

What This Feature Does

Field types determine what kind of data can be collected in your forms. Assignar Pay provides over 20 field types ranging from simple text inputs to complex table structures and resource lookups. Each field type has specific configuration options and validation rules.

Field Categories Overview

Input Fields

Input

A single-line text field for short text entry.

Configuration Options:

• Label: Field label text
• Placeholder: Hint text when empty
• Required: Make field mandatory
• Default Value: Pre-filled text
• Max Length: Character limit

Best For:

• Names
• Short answers
• Reference numbers
• Addresses (single line)

Example Uses:

• "Site Address"
• "Order Number"
• "Supervisor Name"

Textarea

A multi-line text field for longer content.

Configuration Options:

• Label: Field label text
• Placeholder: Hint text when empty
• Required: Make field mandatory
• Default Value: Pre-filled text
• Rows: Number of visible text rows

Best For:

• Detailed descriptions
• Comments and notes
• Incident narratives
• Instructions

Example Uses:

• "Describe the hazard observed"
• "Additional comments"
• "Work completed today"

Password

A masked input field for sensitive data.

Configuration Options:

• Label: Field label text
• Placeholder: Hint text
• Required: Make field mandatory

Best For:

• Security codes
• PIN numbers
• Sensitive identifiers

Note: Password fields mask the input but data is stored. Use for UI masking, not security-critical applications.

OTP

One-time password/verification code input.

Configuration Options:

• Label: Field label text
• Length: Number of digits/characters
• Required: Make field mandatory

Best For:

• Verification codes
• Authorization numbers
• Multi-digit codes

Selection Fields

Select

A dropdown menu for choosing one option from a list.

Configuration Options:

• Label: Field label text
• Options: List of available choices
• Required: Make field mandatory
• Default Value: Pre-selected option
• Placeholder: Text when nothing selected

Best For:

• Single selection from many options
• Categories and classifications
• Status selections

Example Uses:

• "Project Status" (Active, On Hold, Completed)
• "Weather Conditions" (Clear, Cloudy, Rain, Storm)
• "Priority Level" (Low, Medium, High, Critical)

Adding Options:

1. Select the field
2. Find "Options" in configuration
3. Click "Add Option"
4. Enter the option label and value
5. Repeat for all options
6. Drag to reorder if needed

MultiSelect

Select multiple options from a list.

Configuration Options:

• Label: Field label text
• Options: List of available choices
• Required: Make field mandatory
• Default Value: Pre-selected options

Best For:

• Multiple category selection
• Applicable conditions
• Multi-select checklists

Example Uses:

• "PPE Worn" (Hard Hat, Safety Vest, Gloves, Safety Glasses)
• "Trades on Site" (Electrical, Plumbing, HVAC, Framing)
• "Issues Found" (Safety, Quality, Schedule, Budget)

RadioGroup

Select one option from a visible list of choices.

Configuration Options:

• Label: Field label text
• Options: List of available choices
• Required: Make field mandatory
• Default Value: Pre-selected option
• Layout: Horizontal or vertical

Best For:

• Few options (2-5)
• When all options should be visible
• Quick single selection

Example Uses:

• "Inspection Result" (Pass, Fail, N/A)
• "Risk Level" (Low, Medium, High)
• "Shift Type" (Day, Night, Swing)

ToggleGroup

Group of toggle buttons for single selection.

Configuration Options:

• Label: Field label text
• Options: List of available choices
• Required: Make field mandatory
• Default Value: Pre-selected option

Best For:

• Visual button-style selection
• Quick toggles between states
• Compact option selection

Example Uses:

• "Completion Status" (Not Started, In Progress, Complete)
• "Rating" (Poor, Fair, Good, Excellent)

Boolean Fields

Checkbox

A single checkbox for yes/no selection.

Configuration Options:

• Label: Field label text
• Required: Require checkbox to be checked
• Default Value: Checked or unchecked by default

Best For:

• Agreements and acknowledgments
• Single yes/no questions
• Confirmation items

Example Uses:

• "I confirm this information is accurate"
• "Site secured at end of day"
• "Toolbox talk completed"

Switch

A toggle switch for on/off selection.

Configuration Options:

• Label: Field label text
• Required: Make field mandatory
• Default Value: On or off by default

Best For:

• Feature toggles
• Enable/disable options
• Status indicators

Example Uses:

• "Equipment operational"
• "Area cleared for work"
• "Permits obtained"

Numeric Fields

Slider

A sliding scale for numeric values.

Configuration Options:

• Label: Field label text
• Min Value: Minimum selectable value
• Max Value: Maximum selectable value
• Step: Increment between values
• Default Value: Starting position
• Required: Make field mandatory

Best For:

• Range selections
• Percentage values
• Quantity estimates

Example Uses:

• "Completion Percentage" (0-100)
• "Satisfaction Rating" (1-10)
• "Estimated Hours" (1-40)

Rating

Star-based rating selection.

Configuration Options:

• Label: Field label text
• Max Rating: Number of stars (typically 5)
• Required: Make field mandatory
• Default Value: Pre-selected rating

Best For:

• Quality ratings
• Performance scores
• Satisfaction levels

Example Uses:

• "Work Quality Rating"
• "Site Cleanliness"
• "Safety Compliance Score"

Date/Time Fields

DatePicker

Select dates, times, or date ranges.

Configuration Options:

• Label: Field label text
• Mode: Single date, date range, or multiple dates
• Include Time: Add time selection
• Required: Make field mandatory
• Default Value: Pre-selected date
• Min Date: Earliest selectable date
• Max Date: Latest selectable date

Modes:

• Single: Pick one date
• Range: Pick start and end dates
• Multiple: Pick multiple individual dates

Best For:

• Event dates
• Inspection dates
• Scheduled times
• Project periods

Example Uses:

• "Inspection Date" (Single)
• "Project Duration" (Range)
• "Work Hours" (Single with time)
• "Unavailable Dates" (Multiple)

File Fields

FileUpload

Upload files and images.

Configuration Options:

• Label: Field label text
• Accepted Types: File extensions allowed (e.g., .pdf, .jpg, .png)
• Max File Size: Maximum file size in MB
• Max Files: Maximum number of files
• Required: Make field mandatory
• Stamp location & metadata on photos: Burn capture details onto photos (image uploads only)

Photo Location Stamp:

When "Stamp location & metadata on photos" is enabled, each captured photo is saved twice: the untouched original AND a copy with the selected details burnt in, GPS-camera style — map thumbnail, place and street address, GPS coordinates, date/time, a free-text note, user, compass bearing, and (opt-in) the company logo in the top-right corner. Each element is individually toggleable. The stamped copy is what appears in form results, custom prints, and PDF exports; the original stays downloadable from the submission ("Original" link next to the photo).

When the Text note element is on, the form shows a short note input above the photo dropzone (60 characters, kept to a single overlay line); whatever is typed there is burnt onto the photos uploaded with it. The note never overlays more than one line — overlong text is shortened with an ellipsis. The photo itself is never resized by stamping: the overlay is drawn within the original image dimensions, scaled relative to the photo with minimum and maximum bounds so it stays readable without dominating the image.

Stamping requires location services on the capturing device. If location is unavailable or denied, the photo is saved without the stamp and the user sees a warning — the upload itself is never blocked.

A few behaviours worth knowing:

• Mobile camera: when stamping is on and the field accepts only images, a dedicated Take photo button opens the device camera directly. The regular dropzone keeps the full picker — camera roll, files, or the native "Take Photo" option — so previously taken photos can still be uploaded (they're stamped with the upload-time location).
• Multiple photos: with "Allow multiple file uploads" on, every image in the batch gets its own stamp (and its own preserved original). A typed note applies to all photos uploaded with it, then clears.
• Mixed file types: stamping only ever applies to images — PDFs or other documents in the same field upload untouched, and if the field's allowed types are changed to exclude images the stamping option (and note input) deactivates.
• Submit is held during uploads: the form's Submit button shows "Uploading…" and stays disabled until every file (and its stamped copy) has finished uploading, so a submission can never miss an in-flight photo.

Best For:

• Photo documentation
• Document attachments
• Supporting evidence

Example Uses:

• "Site Photos"
• "Permit Documents"
• "Damage Photos"
• "Delivery Receipts"

Accepted Types Examples:

• Images: .jpg, .jpeg, .png, .gif
• Documents: .pdf, .doc, .docx
• All: Leave empty for any file type

Special Fields

Signature

Capture handwritten signatures.

Configuration Options:

• Label: Field label text
• Required: Make field mandatory

Best For:

• Acknowledgments
• Approvals
• Certifications
• Legal agreements

Example Uses:

• "Supervisor Signature"
• "Client Approval"
• "Safety Acknowledgment"

How It Works:

1. User clicks/taps the signature area
2. Draws signature using mouse/finger/stylus
3. Click "Clear" to start over
4. Click "Done" to save
5. Signature is stored as an image

Draw on Image

Let responders annotate a background image with touch- or mouse-drawn strokes — site diagrams, damage photos, as-built markups, and similar visual evidence.

When to use it:

• Everyone should mark up the same site plan or diagram (template image)
• Each responder brings their own photo to annotate (responder upload)
• You need a single saved image that combines the photo and the drawing (not a separate attachment)

Image source (required — choose one in the field configuration):

Template mode requires a template image before the form can be published usefully — responders see a warning if the builder has not uploaded one yet.

Configuration options:

• Label / Description: Field label and helper text
• Required: Make a saved annotation mandatory
• Image source: Template image or Responder uploads
• Template image (template mode): The shared background image
• Image description (template mode): Alt text for accessibility
• Default pen color: Starting stroke color (hex)
• Stroke width: Pen thickness in pixels (1–10)
• Allow responder to change pen color: When on, the fullscreen editor shows a color picker with preset swatches; when off, the default color is fixed

Responder experience:

1. Template mode — the template image loads automatically. Responder mode — tap Upload your image and pick a photo (same formats and 10 MB limit as the template upload).
2. Tap Draw on image to open a fullscreen drawing overlay (optimised for phones and tablets — not a small inline canvas).
3. Draw with finger, stylus, or mouse. Change pen color if the builder allowed it.
4. Clear removes strokes on the current canvas without closing the overlay. Save drawing composites the strokes onto the background and closes the overlay.
5. The inline preview shows the saved composite. Clear on the preview removes the saved annotation so they can start again.

The saved value is a composite PNG (background plus drawing), stored the same way as a Signature field's image data — not a separate file upload field.

Viewing submissions:

• On a submitted form, the field shows the saved composite image in read-only mode (no drawing controls).
• PDF and custom print exports embed the composite image, the same as signatures.

Limitations:

• Cannot be used as a Table column — add it as a top-level field instead.
• Cannot be a pull-through target in Linked Forms (like Signature and Map fields).
• Cannot be referenced in a Calculated field formula.

Example uses:

• "Mark damage on site photo" (responder upload)
• "Locate utilities on site plan" (template image)
• "Sketch work area on aerial" (template image)

Table

Capture tabular data with multiple rows.

Configuration Options:

• Label: Field label text
• Columns: Define table columns with types
• Min Rows: Minimum number of rows required
• Max Rows: Maximum rows allowed
• Required: Make field mandatory

Column Types:

• Text: Free text entry
• Number: Numeric values
• Select: Dropdown selection
• Date: Date picker
• Checkbox: Yes/no toggle

Best For:

• Material lists
• Equipment inventories
• Multiple line items
• Repeated data entry

Example Uses:

• "Materials Used" (Material, Quantity, Unit)
• "Equipment Inspected" (Equipment, Status, Notes)
• "Workers on Site" (Name, Trade, Hours)

Configuring Columns:

1. Select the Table field
2. Click "Add Column"
3. Enter column name
4. Select column type
5. Configure column-specific options
6. Repeat for additional columns

Material to Review

Attach a document or link that the form filler must open before they can submit. Use it to put a policy, SWMS, or training resource directly inside the form so the filler can read it and sign off on it — no more uploading the document elsewhere, copying the link, and pasting it into a hyperlink field.

The material can come from one of two sources:

• External link — a URL to a document or video anywhere on the web (e.g. a hosted policy PDF or a training video).
• Upload PDF — a PDF you upload directly when building the form (e.g. the drug & alcohol policy or a site SWMS). The file is stored securely and opened through a temporary link, so even external users (clients, suppliers, visitors) filling the form can view it.

Configuration Options:

• Label: Field label text
• Description: Optional helper text shown under the label
• Material source: External link or Upload PDF
• Material URL: The link to open (when source is External link)
• PDF document: The uploaded file (when source is Upload PDF; PDF only, up to 25 MB)
• Require acknowledgement: When on (the default), the filler must open the material before the form can be submitted

How It Works:

1. The filler sees an Open link or Open PDF button (with the file name) for the material.
2. They click it; the document or video opens in a new tab.
3. Once opened, the field is marked ✓ Reviewed.
4. If Require acknowledgement is on, the form cannot be submitted until the material has been opened. Turn it off to use the field as plain reference material that doesn't block submission.

Best For:

• Policy and procedure sign-off (drug & alcohol, code of conduct)
• SWMS and safe-work-procedure acknowledgment
• Training documents or induction videos workers must watch
• Any reference material the filler must see before answering

Example Uses:

• "Drug & Alcohol Policy" (upload the PDF, require acknowledgement)
• "Site SWMS" (upload the PDF, require acknowledgement)
• "Watch the induction video before continuing" (external link)

Printed / PDF View:

A submission's PDF copy is a static document, so it does not embed the policy or video. Instead, for each Material to Review field it prints:

• the field label,
• the link URL (for an external link) or the attached file name (for an uploaded PDF), and
• an acknowledgement line: [X] Reviewed if the filler opened the material, or [ ] Not reviewed if they didn't.

This keeps the printed record auditable — it shows which document was attached and whether the worker reviewed it — without trying to reproduce the document itself inside the export. To keep a copy of the source document alongside the submission, attach it with a FileUpload field as well.

Weather

Record the site's weather conditions at the exact moment someone is filling in the form — a live lookup from a connected weather provider, or a hand-entered observation when live capture is not available or does not match conditions on the ground.

What it captures:

A single observation: condition (Clear, Partly cloudy, Overcast, Fog, Drizzle, Rain, Snow, Thunderstorm), temperature, feels-like temperature, wind speed, rainfall, humidity, chance of rain, and — if the field is configured to keep one — a short multi-day forecast captured alongside it. The observation is frozen at the moment it's captured: nothing about a Weather field ever re-fetches or updates once saved, so opening a submission next week, next year, or offline shows exactly what was recorded at fill time, not a live lookup.

Two sources (the responder is never left guessing which is which — every observation shows its source):

Live capture depends on the deployment having a weather provider connected, and the field distinguishes not connected from couldn't check:

In the last state a required field can never be submitted, so the builder warns the author as soon as they mark it required with no provider connected — connect one to resolve it.

Configuration Options:

• Label / Description: Field label and helper text
• Required: Make an observation mandatory
• Allow live capture: Offer the "Capture weather" lookup
• Allow manual entry: Let responders record conditions by hand, including as a correction to a live capture
• Show forecast: Keep a short forecast captured alongside the observation
• Forecast days: How many days of forecast to store (0–5)
• Location source: Look up conditions for the device's own location, or read a location from a Map (Geospatial) field elsewhere on the form

Best For:

• Recording ground conditions on dockets, timesheets, and site diaries
• Gating a wet-weather or heat-stress section behind actual conditions
• Backing up delay claims and stand-downs with a timestamped, point-in-time record

Example Uses:

• "Weather at start of shift"
• "Site conditions at time of pour"
• "Conditions" (paired with a wet-weather section shown only in rain)

How It Works:

1. The responder taps Capture weather (if live capture is allowed) to look up current conditions, or Enter manually to describe them by hand.
2. The saved observation shows an icon, the condition, all captured metrics, its source, and the capture time.
3. Manual entry always replaces the displayed observation with a new, separately-recorded one — it is never treated as an edit of a live capture.

Conditional Logic:

A Weather field can drive show/hide rules directly off the stored observation, using four values from it:

See Conditional Logic for how to set up a rule.

Viewing submissions: A submitted Weather field shows the same observation card as at fill time — icon, condition, metrics, source, and capture time — with no capture controls, since it is a fixed record rather than a live lookup. PDF and custom print exports embed the same details using the app's own icon set; nothing on a Weather field ever requests an image from the weather provider.

Limitations:

• Cannot be used as a Table column — a stored observation is a structured, provenance-bearing snapshot, not a single scalar value.
• Not filled in by AI prefill: a captured or hand-entered observation is evidence of real conditions, and AI has no way to observe the weather, so this field type is excluded from that surface entirely.

Map Fields

Map (Geospatial)

Capture geographic data — points, lines, and polygons — drawn directly on a map, with per-feature attributes and photos.

Configuration Options:

• Label: Field label text
• Allowed geometry types: One or more of Point, Line, Polygon (required)
• Custom base layer URL (optional): XYZ tile URL with {z}/{x}/{y} placeholders for site-specific aerial / customer-supplied basemaps
• Per-feature attributes: Define one or more attributes captured against each shape (any of: text, number, select, multi-select, date, checkbox, switch, photo)

What the form filler does:

1. Picks a drawing mode from the toolbar (Point, Line, Polygon, or Use my location for GPS-tagged points)
2. Clicks on the map to drop a point, draw a line vertex-by-vertex, or close a polygon
3. Names the feature (e.g. "Hydrant near gate") and picks a color — from a curated palette or any custom color via the "+" swatch (color wheel / hex)
4. Fills in the attributes (including attaching photos)
5. Repeats for as many features as needed before submitting

Best For:

• Service locating (gas / comms / power / water with depth + photo per feature)
• As-builts (pipework runs, fence lines, work areas)
• Site inspections (defect pins with severity + photo)
• Compound / exclusion zones (polygon with reason + dates)

Example Uses:

• "Located utilities" (point per utility, plus type + depth + photo)
• "Work area" (polygon outlining the compound)
• "Damaged sections" (line traced over the damaged run)
• "Daily check-in" (single GPS-tagged point at job start)

Viewing submissions: Map-field submissions render every feature on a read-only map with the captured color and name; clicking a feature opens the read-only attribute panel including photo thumbnails. The submissions table shows the feature count (e.g. "14 features") for each row.

For drawing controls, troubleshooting, and worked configuration examples, see the dedicated Map (Geospatial) Field guide.

Resource Fields

Resource

Select from internal business data like projects, clients, workers, and equipment.

Configuration Options:

• Label: Field label text
• Resource Type: Type of data to select from
• Required: Make field mandatory
• Filters: Optional filters to narrow options
• Cascading Filters: Filters based on other field values

Available Resource Types:

• Projects
• Clients
• Workers
• Equipment
• Cost Codes
• Activities
• Custom resources (configured by admin)

Best For:

• Linking forms to business data
• Consistent data selection
• Cross-referencing records

Example Uses:

• "Select Project" (links submission to project)
• "Assigned Worker" (select from worker list)
• "Client" (select from client list)

Cascading Filters: Resource fields can filter based on other field values:

1. First field: Select "Client"
2. Second field: Select "Project" filtered by selected Client
3. Projects dropdown only shows projects for the selected client

See Conditional Logic for more on cascading behavior.

Static Elements

Text

Display static text, headings, or instructions.

Configuration Options:

• Content: The text to display
• Variant: H1, H2, H3, or Paragraph

Variants:

• H1: Large heading
• H2: Section heading
• H3: Subsection heading
• P: Regular paragraph text

Best For:

• Form instructions
• Section introductions
• Warnings and notices
• Help text

Example Uses:

• "Complete all fields marked with *"
• "Section 2: Safety Observations"
• "Important: Report all incidents within 24 hours"

Separator

A horizontal line to visually separate content.

Configuration Options:

• Style: Line style (solid, dashed, etc.)

Best For:

• Visual breaks between sections
• Grouping related fields
• Improving form readability

Field Validation

All fields support validation options:

Required Validation

• Toggle "Required" to make the field mandatory
• Form cannot be submitted until field is completed
• Required fields show an asterisk (*) next to their label

Type-Specific Validation

• Input: Min/max length, pattern matching
• Numeric: Min/max values
• DatePicker: Min/max dates
• FileUpload: File types, max size, max count

Custom Validation Messages

• Override default error messages
• Provide specific guidance for users

Tips for Choosing Field Types

• Use Select for 5+ options, RadioGroup for fewer
• Use Textarea for descriptions, Input for short answers
• Use Table for repeated data, not multiple similar fields
• Use Resource for business data, not manual entry
• Use DatePicker with appropriate mode for your date needs
• Use Signature for legal acknowledgments
• Use Draw on Image when markups belong on a photo or diagram, not as a separate attachment
• Use Weather to record point-in-time site conditions, not a Select field, when you need a timestamped, provenance-tracked observation (and want conditional logic on temperature, rain, or wind)
• Use Text elements for instructions throughout the form

What's Next

After understanding field types, you may want to:

• Learn how to create forms in the Form Builder
• Add dynamic behavior with Conditional Logic
• Set up Workflows for form automation
• Configure Permissions for access control