Custom Fields for Client and Project Records
Standard screens rarely match every contractor's workflow. Custom fields let a team add the details it actually tracks — without waiting for a generic field that may not fit most users — and place them on client or project records where the work is managed.
Why add fields you control?
Instead of expanding every screen with fields only some teams need, custom fields give each company control over its own data model. A team can add a field for a detail that matters locally, leave it out where it does not, and keep the shared screens cleaner for everyone else.
That distinction matters when planning: a custom field is not a one-off note on a single record. It is a reusable entry point, created once and then available wherever that record type is used.
Setup checklist
Use this sequence to set up a field without creating clutter:
- Decide the record type first: client screen or project screen.
- Name the field for the exact detail your team will enter, not a vague label.
- Choose single-line text for short values and multi-line text for longer notes.
- Save the field and check that it appears on client or project records as intended.
- Tell the team what to enter, when, and whether it is required for their workflow.
A useful planning check is to ask whether the detail is needed on every record of that type. If it is only relevant to one job, a note may be better than a permanent field. If it recurs across many records, a custom field gives it a consistent home.
Where fields live and what they do
Field map
- Location: Configure page, under the Admin menu in the main navigation
- Configuration area: Custom Fields box
- Placement options: client screen or project screen
- Launch field types: single-line text field; multi-line text field
- Planned later: custom dropdown fields with defined options
- Effect of saving: field becomes available on all relevant client or project records
For example, a team might add a single-line field to capture a short reference that is checked quickly on every project, and a multi-line field for longer context that needs more space. The same setup logic applies to client records: choose the placement first, then the type that matches the length of the answer.
Keeping custom fields useful
Custom fields work best when they are introduced deliberately. Start with the details your team asks for repeatedly, confirm the field appears in the right place after saving, and review whether the label still matches how people use it. Feedback from daily users is the best guide for future improvements — if a field is confusing, unused, or duplicating another entry, rename, repurpose, or remove it rather than letting screens accumulate.
Frequently asked questions
Where do I create a custom field?
Go to Configure under the Admin menu in the main navigation, open the Custom Fields box, create the field, and save it. It then appears on the relevant client or project records.
What field types were available at launch?
At the time of this announcement, single-line text and multi-line text fields were available. Custom dropdown fields, with user-defined options, were planned for a later release rather than available immediately.
Does a new field appear on every record?
Yes. Once a field is saved, it becomes available across all client or project records, depending on where you placed it, so teams do not need to recreate it record by record.