Custom Fields
Custom fields let you track information specific to your business that ACOS doesn't model out of the box — a referral source, a contract number, an internal risk rating. Define the field once in Settings, then fill in a value on every Deal or Contact.
Two Kinds of Custom Field Data
Custom fields work on two levels. Definitions are created once by an Admin or Owner in Settings → Custom Fields — they set the label, type, and whether the field is required. Values are filled in per record — every Deal and Contact gets its own answer for each defined field.
Custom fields can be added to two entity types only: Deals and Contacts. Projects, Tasks, and Invoices do not currently support custom fields.
Field Types
| Type | Input | Notes |
|---|---|---|
| Text | Free text | Any string, no length validation beyond the label field itself |
| Number | Numeric input | Stored as a plain number — no currency formatting |
| Date | Date picker | Stored as ISO date |
| Select (dropdown) | Single choice | Options are set once when you create the field, comma-separated |
| Yes / No | Toggle | Boolean true/false |
Creating a Field Definition
Go to Settings → Custom Fields
Choose the Deals or Contacts tab depending on which entity you want to extend.
Click Add Field
A form appears with Label, Type, and — for Select fields — an Options input.
Enter a label and pick a type
For a Select field, enter options as a comma-separated list, e.g. "Referral, Inbound, Cold Outreach".
Toggle Required if needed
Required fields must be filled in before the record can be saved from the UI.
Save
The field is now available on every Deal or Contact of that entity type, organization-wide.
Filling in Values
Open any Deal or Contact detail page — the Custom Fields section appears in the overview tab, listing every defined field for that entity type with an input for its value. Values are saved per record; two Deals can have completely different answers for the same custom field.
When you fetch a Deal or Contact from the API, its custom field values are returned as a flat { label: value }map alongside the record's normal fields — you don't need a separate lookup to read them.
Deleting a Field Definition
Deleting a custom field definition is permanent and removes every saved value for that field across every Deal or Contact, organization-wide. There is no undo. If you only want to stop showing a field going forward, consider renaming it to indicate it's deprecated instead of deleting it.
Roles & Permissions
| Action | Member | Manager | Admin | Owner |
|---|---|---|---|---|
| View custom field values on records they can access | ✓ | ✓ | ✓ | ✓ |
| Edit custom field values | ✓ (records they can edit) | ✓ | ✓ | ✓ |
| Create / edit / delete field definitions | ✗ | ✗ | ✓ | ✓ |
FAQ
Can I reorder custom fields?
Field definitions are created with a position value, but there is currently no drag-to-reorder UI in Settings. Fields display in the order they were created.
Can I add custom fields to Projects or Tasks?
Not currently. Custom fields are scoped to Deals and Contacts only.
What happens to values if I change a Select field's options?
Existing saved values are not automatically remapped. If you remove an option that a record already has selected, that record keeps the old value on file even though it's no longer a valid choice going forward — update the affected records manually.
Can I filter Deals or Contacts by a custom field value?
Custom field values are returned with every Deal and Contact record, but there is currently no dedicated filter UI for custom fields in the CRM list views.