How do I set a custom field to appear in a specific Stage?

Custom Fields can appear in one or multiple Stages. When creating or editing a Custom Field you may select specific Stages to ensure your fields are only displayed where they are needed. 

Here are step-by-step instructions on how to create a new Custom Field and select a specific Stage in which it will appear. In this example we'll show you how to set a Lost Reason on Deal. 

1.) Tap on More (...) in the lower right of your screen on mobile (iOS/Android) and lower left on


2.) Tap on Settings


3.) Scroll down to the Customizations section and tap on Custom Fields to expand the section. 

4.) Tap on the gear icon next to the section where you wish to add Custom Fields. You can create and edit Custom Fields for People, Companies, and Projects (or Deals, Cases, Sales etc...)

5.) Along the top of the screen tap on the Add button and then select Field. 

6.) Then name your field and select and select the Data Type from the dropdown.

In this example we have selected "Pick List" for a new field called "Lost Reason". This field will have several values that can be selected so the Pick List field is the best option.

Only on value will be set so the "One" option is used. If you would like the ability to select multiple values than select "Many".

7.) Select the Cloze sections where you would like your new field to appear.

In this example the "Lost Reason" field will appear on profiles in the People and Companies sections, and in the Deals section. Tap on Company, People or Deals (or Projects, Cases, Sales etc...) to make your selection. 

8.) Next you can select the Segments and Stages where you would like your new Custom Field to appear. Tap on the funnel icon make your selection. 

In this example the "Lost Reason" field will only appear in the Customers and Deals Segments.

In this example the Lost Reason field will only appear in the Lost Stage for Customers and Deals Segments. 

9.)  Tap on Save when you are done. 




Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.