Custom fields give contacts, deals, and tasks a consistent place for information your team needs, such as a renewal date or service category. Prefer a field for information you will filter or compare; use notes for a longer explanation.
Create a field#
- Open Settings, then Objects, and choose the relevant object.
- In Fields, choose New field. Field configuration requires an owner or admin.
- Select a type, give the field a clear Name, and optionally add a Description.
- Configure any choices or date options, then save. Use the page’s View settings to show the field in its table or deal cards.
You can also create fields from View settings when that action is available. Reordering fields in Settings changes their order on records; choosing visible columns is a separate display decision.
Pick a supported type#
Common choices include Single line text, Long text, Single select, Multiple select, Person, Date, and URL. Select options need nonempty, distinct names. Created and modified metadata fields are filled in for you, rather than manually edited.
There are 50 fields per object, including built-in fields. Names are limited to 60 characters and descriptions to 400. Built-in field identities are protected. Although Button is offered, clicking a button field does not run an action.
Use lookups instead of copying#
A Lookup displays a field through an existing contact–deal relationship. Choose Relationship, then Source field. On a contact, it shows values from every linked deal; on a deal, it shows the linked contact’s value.
Lookup values are read-only: edit the source record to change them. Lookups are not available for Tasks, and another lookup or a button cannot be the source. Create a new lookup rather than converting an existing ordinary field into one.
Change or remove fields carefully#
A field’s type is locked while records contain values or dependent lookups use it; lookup types themselves remain locked. Remove dependent lookups before deleting their source field. Saved or default filters using a lookup must be removed before changing its source or deleting it.
Deleting an ordinary field permanently erases its stored values. Deleting a lookup removes the display field, not the values on the source records. Hiding a field in View settings is the safer choice when you only want less clutter.