What are configurable fieldsets and which Procore tools support them?
A configurable fieldset is a group of fields in certain Procore tools that can be set to optional, required, or hidden, depending on the needs of your company. This allows for better control over data entry when users create and edit items in Procore projects. To configure fieldsets, you must have 'Admin' permissions to the Company Admin tool.
Notes:
- You can configure fields for the Create and Update project pages. However, only one fieldset can be created, and it will be applied to all projects. See Create a Default Project Fieldset.
- Through configurable fieldsets, you can also create custom fields for certain tools in Procore to use on projects. See Create New Custom Fields.
- If a field that is not currently supported on the Procore mobile app is marked as 'Required,' the unsupported field will not appear on the mobile app and the item can still be submitted without the required field. Items created and edited on the web application will still require the 'Required' fieldset regardless of whether the field is supported on the mobile app.
Prerequisites
See Create New Configurable Fieldsets OR click here to view the steps.
Supported Tools
The following Procore tools support configurable fieldsets:
Tool | Fieldsets Available to Configure | List of Fields |
---|---|---|
Admin (Project level) | Project fieldset Note: Only one fieldset can be configured for the project page and the configured fieldset will automatically apply to all projects. |
Which fields on the project page can be configured as required, optional, or hidden? |
Coordination Issues | General Information fieldsets | Which fields in the Coordination Issues tool can be configured as required, optional, or hidden? |
Correspondence | Correspondence Type fieldsets Note: Each of your company's custom correspondence types has its own fieldset. |
Which fields in the Correspondence tool can be configured as required, optional, or hidden? |
Daily Log |
Manpower Log, Notes Log, Daily Construction Report Log, Observed Weather Conditions, and Visitor Log fieldsets |
Which fields in the Daily Log tool can be configured as required, optional, or hidden? |
Directory |
Person and Company fieldsets |
Which fields in the Directory tool can be configured as required, optional, or hidden? |
Documents (Project Documents) | Documents fieldsets Note: Currently, the only changes available for a Documents fieldset are adding or removing custom fields. |
Which fields in the Documents tool can be configured as required, optional, or hidden? |
Drawings | Drawing Revision fieldsets | Which fields in the Drawings tool can be configured as required, optional, or hidden? |
Incidents |
Incident, Injury/Illness, Property Damage, Environmental, Near Miss, Witness Statement, and Action fieldsets |
Which fields in the Incidents tool can be configured as required, optional, or hidden? |
Inspections |
Unassociated, Quality, Safety, Commissioning, and Environmental fieldsets |
Which fields in the Inspections tool can be configured as required, optional, or hidden? |
Observations |
Commissioning, Environmental, Quality, Safety, Warranty, and Work to Complete fieldsets
|
Which fields in the Observations tool can be configured as required, optional, or hidden? |
Punch List |
Punch Item fieldsets |
Which fields in the Punch List tool can be configured as required, optional, or hidden? |
RFIs |
RFI fieldsets |
Which fields in the RFIs tool can be configured as required, optional, or hidden? |
Specifications | Specification Section Revision fieldsets | Which fields in the Specifications tool can be configured as required, optional, or hidden? |
Submittals | Submittal Log fieldsets | Which fields in the Submittals tool can be configured as required, optional, or hidden? |
T&M Tickets | General Information, Labor, Material, and Equipment fieldsets | Which fields in the T&M Tickets tool can be configured as required, optional, or hidden? |