Who This Is For / When to Use
Use Conditional Custom Fields when opportunity forms should change based on the details of each deal.
This feature is useful when you need to:
Show fields only when they are relevant.
Require information at a specific pipeline stage.
Collect different information for different pipelines.
Require additional information before an opportunity can be saved.
Standardize opportunity data collection across teams.
For example, you can require Proposal Amount, Expected Close Date, and Decision Maker when an opportunity moves to the Closed stage.
What Conditional Custom Fields Can Do
Admins can create rules that control which opportunity fields appear and which fields must be completed.
A conditional rule contains:
Trigger(s): The conditions that determine when the rule applies.
Outcome(s): The fields or folders Kyrios shows or makes mandatory when the trigger conditions are met.
Multiple conditional rules can exist for Opportunity fields.
The Conditional rules tab displays each rule's triggers, outcomes, and last modified information.
Supported Trigger Fields
Conditional rules can use the following opportunity fields as triggers:
Pipeline
Pipeline stage
Status
Dropdown fields
Radio fields
Checkbox fields
Multi-select fields
Rules can use a single condition or multiple conditions connected with AND/OR logic.
The rule builder includes a live preview so you can see which fields will appear while configuring the rule.
Available Rule Outcomes
A conditional rule can use these outcomes:
Show field — Displays an individual field when the rule conditions are met.
Show folder — Displays an entire folder of fields when the rule conditions are met.
Make mandatory — Requires a field to be completed when the rule conditions are met.
You can add multiple outcomes to the same rule.
For example, a rule can make Proposal Amount, Expected Close Date, and Decision Maker mandatory when an opportunity reaches a specific pipeline stage.
How Show Rules Work
Fields and folders included in a Show rule are hidden by default. They become visible only when the rule's trigger conditions are met. Fields that are not included in a Show rule remain visible as usual.
This means you do not need to create a separate rule to hide a field before its conditions are met. The rule builder indicates when a field will remain hidden until its Show rule is satisfied.
How Mandatory Rules Work
A Make mandatory outcome requires the selected field to be completed when the rule conditions are met. If the required information is missing, the opportunity cannot be saved through supported web or mobile opportunity forms.
When multiple rules apply at the same time, their mandatory requirements are combined.
For example, when a rule requires three fields for the Closed stage, Kyrios can prompt the user to complete those fields before moving the opportunity to that stage.
Mandatory fields also appear directly in the opportunity editing experience when their rule conditions are met.
How to Create a Conditional Rule
Go to Settings → Custom Fields.
Select Opportunity.
Open the Conditional rules tab.
Click Create conditional rule.
The Opportunity Conditional Rules area displays existing rules and provides examples of common rule configurations.
Under Trigger(s), choose the field that should control the rule.
Select the comparison operator and value.
Add additional conditions if needed and connect them using AND/OR logic.
Under Outcome(s), select:
Show field
Show folder
Make mandatory
Select the field or folder affected by the outcome.
Add additional outcomes if needed.
Review the Preview logic panel.
Click Save rule.
Saved rules take effect immediately.
How to Manage Rules From a Pipeline
Conditional rules can also be accessed directly from the Pipelines settings.
Go to Settings → Opportunities & Pipelines.
Find the pipeline you want to manage.
Open the pipeline's Actions menu.
Select Manage conditional rules
Pipeline-specific access makes it easier to manage rules while configuring the sales process they apply to.
Where Conditional Rules Apply
Conditional Opportunity field rules apply to:
Add Opportunity flows
Edit Opportunity flows
Bulk Edit flows
Supported web experiences
Supported mobile experiences
Validation does not apply to:
Public API updates
Workflow-based updates
An opportunity updated through the Public API or a workflow is not blocked by mandatory-field validation from these rules.
Permissions and Account Behavior
Only Admins can create, edit, or delete Conditional Custom Field rules. Rules are configured separately for each account.
Creating a rule in one account does not automatically configure the same rule in another account. Nothing changes for opportunity forms until an Admin creates the first rule.
Common Issues and Fixes
A field is hidden even though I did not create a Hide rule
Fields included in a Show field or Show folder rule are hidden by default until that rule's conditions are met. A separate Hide rule is not required.
A field is still visible when a rule does not apply
Fields that are not referenced by a Show rule remain visible normally.
Only fields or folders controlled by a Show outcome become conditionally hidden.
Multiple required fields appear at the same time
If multiple conditional rules apply to the opportunity, their mandatory requirements are combined. The opportunity must satisfy all active mandatory requirements before it can be saved through supported web or mobile flows.
An API or workflow update saved without completing a mandatory field
Mandatory-field validation applies to supported web and mobile saves.
It does not block Public API or workflow-based updates.
Conditional rules are enabled but nothing changed
Enabling Show & Require Opportunity Fields Conditionally in Labs only makes the feature available. An Admin must create and save at least one conditional rule before opportunity field behavior changes.