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 creating a Project. These fields can be edited in the project's Admin tool. However, only one fieldset can be created, and it will be applied to all projects. See Create a 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' field regardless of whether the field is supported on the mobile app.
Custom fields added to a configurable fieldset are only available for some tools on the Procore mobile app. See What are custom fields and which Procore tools support them?
Supported Tools
The following Procore tools support configurable fieldsets:
Procore Project Tool | Configurable Fieldset | List of Fields | Notes |
|---|---|---|---|
Admin | Project | Which fields on the project page can be configured as required, optional, or hidden? | One (1) global fieldset for all new and existing projects. |
Action Plans | General Information | Which fields in the Action Plans tool can be configured as required, optional, or hidden? | One (1) fieldset per Action Plan Type. |
Budget (Budget Changes) | General Information | Which fields in the Budget tool can be configured as required, optional, or hidden? | |
Change Events | General Information | Which fields in the Change Events tool can be configured as required, optional, or hidden? | Requires Change Management. One (1) fieldset for the Change Events tool. |
Coordination Issues | General Information | Which fields in the Coordination Issues tool can be configured as required, optional, or hidden? | One (1) fieldset for the Coordination Issues tool. |
Commitments | Purchase Orders and Subcontracts | Which fields in the Commitments tool can be configured as required, optional, or hidden? | One (1) fieldset for each Commitment Type. |
Correspondence | Correspondence Type | Which fields in the Correspondence tool can be configured as required, optional, or hidden? | Each Correspondence Type has one (1) fieldset. |
Daily Log | Accident Log, Call Log, Delay Log, Delivery Log, Dumpster Log, Inspection Log, Plan Revision Log, Productivity Log, Quantity Log, Safety Violation Log, Waste Log, Work Log, Manpower Log, Equipment Log, Notes Log, Daily Construction Report Log, Observed Weather Conditions, and Visitor Log | Which fields in the Daily Log tool can be configured as required, optional, or hidden? | One (1) fieldset per Daily Log Type. |
Directory | Person and Company | Which fields in the Directory tool can be configured as required, optional, or hidden? | |
Documents (Project Documents) | Documents | Which fields in the Documents tool can be configured as required, optional, or hidden? | Custom fields are always optional (cannot be marked as required). |
Drawings | Drawing Revisions | Which fields in the Drawings tool can be configured as required, optional, or hidden? | Data entry is revision-specific. Entries do not carry over to new revisions. |
Equipment | Equipment Category | Which fields in the Equipment tool can be configured as required, optional, or hidden? | One (1) fieldset per Equipment Category. |
Incidents | Incident, Injury/Illness, Property Damage, Environmental, Near Miss, Witness Statement, and Action | Which fields in the Incidents tool can be configured as required, optional, or hidden? | One (1) fieldset per Incident Type. |
Inspections | Unassociated, Quality, Safety, Commissioning, and Environmental | Which fields in the Inspections tool can be configured as required, optional, or hidden? | One (1) fieldset per Inspection Type. |
Invoicing (Progress Billings) | Subcontractor Invoices | Tool name may vary by company. See What tool names and terms are different in Procore for general contractors, owners and specialty contractors? | |
My Time | My Time | Which fields in the My Time tool can be configured as required, optional, or hidden? | This functionality is only available when your company is licensed for Procore's Resource Tracking tools. |
Observations | Commissioning, Environmental, Quality, Safety, Warranty, and Work to Complete | Which fields in the Observations tool can be configured as required, optional, or hidden? | |
Prime Contracts (Client Contracts, Funding) | Prime Contracts | Which fields in the Prime Contracts tool can be configured as required, optional, or hidden? | Tool name may vary by company. See What tool names and terms are different in Procore for general contractors, owners and specialty contractors? |
Punch List | Punch Item | Which fields in the Punch List tool can be configured as required, optional, or hidden? | One (1) fieldset for the Punch List tool. |
RFIs | RFI | Which fields in the RFIs tool can be configured as required, optional, or hidden? | One (1) fieldset for the RFIs tool |
Specifications | Specification Section Revision | Which fields in the Specifications tool can be configured as required, optional, or hidden? | One (1) fieldset for the Specifications tool. |
Submittals | Submittal Log | Which fields in the Submittals tool can be configured as required, optional, or hidden? | One (1) fieldset for the Submittals tool. |
T&M Tickets | General Information, Labor, Material, and Equipment | Which fields in the T&M Tickets tool can be configured as required, optional, or hidden? | One (1) fieldset for each listed section. |
Timesheets | Labor and Equipment | Which fields in the Timesheets tool can be configured as required, optional, or hidden? | One (1) fieldset for the Timesheets tool. |
See Also
Loading related articles...