Custom fields let admins capture the information your teams need on each job, such as contact details, job scope or tank size. You create a field once, group it with related fields, and reuse it across activities so it behaves the same way everywhere.
Use custom fields to:
- Add your own fields to jobs
- Group related fields into reusable sets
- Control which fields appear for each activity
- Manage dropdown options in one place
- Show or hide fields based on other answers
The building blocks
Custom fields are built from four pieces that fit inside each other.
| Building block | What it is | Example |
|---|---|---|
| Custom field | A single piece of information users fill in on a job | Contact name, Tank size |
| Option list | A reusable set of options for a dropdown or radio field | High / Medium / Low |
| Fieldset | A reusable group of fields that belong together. A fieldset can include other fieldsets, one level deep. | Billing: Customer name, Billing code, Cost center |
| Activity | The type of job that a fieldset is attached to | Tank delivery |
Fields only appear on a job once their fieldset is attached to that job's activity. Changing a shared field, fieldset or option list can affect every activity that uses it. Custom fields are separate from job forms, which are set up independently.
Before you start
To set up custom fields, you need the Manage custom fields toggle turned on for your user. This toggle is only available for users with the Admin role, and it can only be turned on by IronSight. It’s usually given to a few admins in your organization. Users who only fill in jobs don’t need it.
To request access, contact IronSight Support at support@ironsight.app.
In the Admin Portal, select your hub from the Hubs list on the left, then open the Fields, Field Sets or Option Lists tab. Fields, fieldsets and option lists belong to the hub you select.
How setup works
Setting up custom fields takes five steps, in this order:
- Create option lists for any dropdown/radio, grouped dropdown or creatable selector fields. You can also create one while setting up a field.
- Create your fields. Check whether a field already exists before making a new one. A field's key and type can't be changed after you save it.
- Group fields into fieldsets. This is also where you can change a field's settings, such as making it required, for that fieldset only.
- Add conditions if a field should only appear based on another field's answer.
- Attach fieldsets to activities. Use Preview fields to check the fields, then save the activity. New jobs for that activity show the fields.
Example: Set up tank delivery fields
Here is how the five steps come together for a delivery job that collects contact details and, when needed, tank size.
- Create option lists: Job scope options and Tank size options.
- Create fields: Contact name, Contact phone, Job scope and Tank size. Add the option lists to Job scope and Tank size.
- Create fieldsets: Contact details (Contact name, Contact phone) and Delivery details (Job scope, Tank size).
- Add a condition: in Delivery details, show Tank size only when Job scope is Tank delivery.
- Attach fieldsets: attach both fieldsets to your delivery activity, preview them, and save the activity.
Related articles
- Create fields and option lists: field types, settings, and when to reuse a field instead of creating a new one.
- Build fieldsets and attach them to activities: nesting, conditions, fieldset and activity overrides, and troubleshooting.
Have questions? Contact us at support@ironsight.app and we’ll help you out.