Project Field Settings

Background

Every organization runs projects a little differently, but the project form used to ask everyone for the same information — Client, Owner, Architect, Project Type, Department, Region, Project Lead, Job No., Stage, Location, Description, Delivery Method, Division, Value, Scope, and Dates. Project Field Settings lets you shape that form around your own workflow. From a single panel in Org Settings, you can show or hide any project field, mark the ones your org can't operate without as required, and drag fields into the order your team actually fills them in. Your configuration applies everywhere project fields appear: the Create Project modal, the Edit Project modal, and the columns on the Projects table.

Things to Consider

• Settings are org-wide. One configuration applies across your entire organization. There is no way to set different field settings for individual teams, and the panel does not appear on Team Settings.

• Hiding a field never deletes data. Values already saved on existing projects are preserved and reappear if you turn the field back on.

• Required applies going forward only. Marking a field required affects new projects and future edits. Existing projects missing that field are not blocked or flagged.

• You can't edit the values inside a field. This feature controls whether a field is shown, required, and where it sits — not what options appear in lists like Region or Department. Custom value lists are planned as a future improvement.

• Group By follows visibility, not order. Hidden fields are removed from the Projects table's "Group by" menu, but your custom field order does not carry over to it. Field order does apply to the table's columns.

• Start Date and End Date move together. Dates are treated as a single field, so they are shown, hidden, reordered, and required as one unit.

• Some fields have their own permission or feature requirements. Client, Department, Project Type, Owner, Architect, and Region require read access to their associated scope, and Project Lead requires Smart Folders to be enabled. A field turned on in settings may still be hidden from users who lack the underlying access.

Steps

1. Go to Org Settings → General.

2. Scroll down to the Project Field Settings section.

3. Use the Switch on a field's row to show or hide that field. Note: Hiding a field automatically clears its Required setting, since a hidden field can't be mandatory.

4. For any field that is shown, check the Required box if it should be mandatory. Users will not be able to save a project until required fields are completed.

5. Drag a field's row up or down to change where it appears. This order is reflected in the Create Project modal, the Edit Project modal, and the Projects table columns.

6. Your changes apply immediately — there is no save or publish step. Open the Create Project modal, the Edit Project modal, or the Projects table to confirm the update.