Show or require opportunity fields conditionally
Conditional rules show or hide specific opportunity fields and folders, and make specific visible fields mandatory, based on values your team enters. Only Admins can build these rules, and nothing changes until the first rule is created. Only Admins can build these rules, and nothing changes until the first rule is created.
Before you start
Only Admins can create, edit, or delete conditional rules. Rules are configured separately for each organization, and nothing changes in any workflow until an Admin creates the first rule. The Labs flag for the feature must also be enabled first (see below).
Enable the feature
Turn on conditional fields before you can build any rules.
Go to Settings > Labs.
Enable Show & Require Opportunity Fields Conditionally for the organization.
Create a conditional rule
You can open the rule builder from two places. Either path reaches the same Create conditional rule screen.
Open the rule builder. Go to Settings > Custom Fields > Opportunity > Conditional Rules and click Create conditional rule. Alternatively, go to Settings > Opportunities & Pipelines, open the Actions menu for a pipeline or stage, and select Manage conditional rules.
Set the trigger conditions. Choose conditions from the Pipeline, Pipeline stage, Status, Dropdown, Radio, Checkbox, or Multi-select fields, and connect them with AND or OR logic.
Choose the outcome. Select Show field, Show folder, or Make mandatory for the fields the rule affects.
Review and save. Check the live preview to confirm how the rule will behave, then click Save rule.
How rules behave
Rules activate immediately after saving. Fields included in a Show rule stay hidden until their trigger conditions are met, while fields not included in any Show rule remain visible as usual. When multiple rules apply, their Make mandatory requirements are combined, so a field can become required even if only one of several matching rules demands it.
Where rules apply
Rules apply to the Add, Edit, and Bulk Edit flows for opportunities, on both web and mobile. Validation is enforced on web and mobile saves, but not on updates made through the Public API or workflow-based updates.
For more on working with opportunity records, see Understanding Opportunities and Create an Opportunity.