---
title: Validation rules | Lightfield
description: Require fields, files or linked records before a record is saved or moves stage, and fix saves that show Requirements not met.
---

A validation rule holds a record back until it has what your process needs, such as a close date before an opportunity moves to Closed won, or a signed contract file before onboarding starts. You set rules on accounts, contacts, opportunities and custom objects.

## Who can use it

Only owners and admins create, edit and delete rules. Members see what a rule needs when it holds back their change.

## Create a rule

Each object can have up to 10 rules. A rule has conditions that decide when it applies and requirements that must all be met while it does. With no conditions, the rule shows **Always** and applies to every record. A requirement can be:

- a field that must be filled, or a checkbox that must be checked
- a number of files, or of linked records such as contacts on an opportunity, with **at least** a minimum count
- a field on linked records, checked **for all**, **for at least one** or **for none** of them

1. In [Settings → Data model](https://crm.lightfield.app/crm/settings/data-model/), choose the object and open the **Rules** tab.
2. Click **Create rule** and enter a **Name**. Members see this name when a save is refused, so describe what the rule protects, for example “Closed won needs a close date”.
3. Under **Conditions**, choose when the rule applies, such as the stage being Closed won. To narrow it, click **+** beside **Conditions** and add another; all of them must match.
4. Under **Requirements**, choose what the record must have. Click **+** beside **Requirements** to add another.
5. Click **Save**.

The rule appears on the **Rules** tab with its **Condition** and **Requirement**.

### Set requirements from a field or a stage

You can also create rules where you edit the field or stage they’re about:

- **A field.** In the field’s settings, turn on **Required field** to require it on every record, or turn on **Set requirements to update this field** to require other fields when this one changes to a value you choose. **Required field** doesn’t appear while the field’s **Enrichment** is on **Suggest** or **Auto**, because enrichment fills it after the record is created. A field with **AI fill** on can still be required.
- **A stage.** In [Settings → Pipelines](https://crm.lightfield.app/crm/settings/pipelines/), turn on **Set requirements to update this stage** on the stage. See [Pipelines](/help/settings/pipelines/index.md#set-up-stages).

These rules are listed on the **Rules** tab too. You edit each one where you made it, and its menu on the **Rules** tab opens that field’s or stage’s settings.

## What happens when a change breaks a rule

Rules check the change being made:

- **Creating a record.** Only fields marked **Required field** are checked, so a new record can start out breaking other rules.
- **Editing a record.** A change is refused only when the record met its rules before the change and the change breaks one. A record that already breaks a rule can still be edited, so you can fix it in steps.
- **Changing a linked record.** A change can also be refused when it would break a rule on the records linked to it, such as removing the last contact from an opportunity that requires one. Lightfield shows **This change affects other records** and names them.

When a member’s change is refused, Lightfield shows **Updates required** so they can fill in what’s missing and save. When it can’t offer that, it shows **Requirements not met** with each rule the record breaks and what’s missing.

Owners and admins are checked when they edit on a record page, side panel, table or board, and they can choose **Save anyway**. Their changes through the agent or the API aren’t checked.

A record that breaks a rule shows a banner, such as **2 requirements need attention**. Click **Review** to see each rule it breaks and what’s missing.

### Imports, syncs and automations

Mail and calendar sync, imports and enrichment are never held back by rules. An automation that runs for the whole workspace is held to rules the way a member is, with no **Save anyway**, and one that runs as a person is checked as that person. When a rule refuses an automation’s change, nothing is saved, the run says which rule or field was missing, and it isn’t retried, so update the record or the rule, then run the automation again. See [Runs and held runs](/help/automations/runs-and-held-runs/index.md).

## Ask the agent

Owners and admins can ask the agent in chat to set rules up, for example “Make Close date required on opportunities” or “Require a contact before a deal enters Proposal”. The agent shows the change in chat; choose **Apply** to save it.

Anyone can ask the agent which records break their object’s rules, for example “Which open opportunities are missing requirements?” It checks only records that person can see.

## Edit or delete a rule

On the **Rules** tab, open the rule’s **Actions** menu and choose **Edit** or **Delete rule**. Deleting a rule can’t be undone.

Lightfield won’t archive a field, relationship or object, or remove a select option or stage, while a rule uses it. The message names those rules; remove it from them, then try again.

## Troubleshooting

### I don’t see the Rules tab

Tasks and Notes don’t take rules, so they never have a **Rules** tab. If accounts, contacts, opportunities or a custom object have no **Rules** tab, your plan doesn’t include validation rules, and the requirement settings on fields and stages don’t appear either. An owner or admin can change plans in [Settings → Billing](https://crm.lightfield.app/crm/settings/billing/).

### Create rule is greyed out

The object already has 10 rules, and hovering shows **An object can have up to 10 rules**. Combine rules that share conditions, or delete one you no longer need.

### A rule didn’t stop a record from being saved

Check the record’s state and who made the change against [What happens when a change breaks a rule](#what-happens-when-a-change-breaks-a-rule). A rule isn’t checked on a new record unless it marks a **Required field**, on a record that already broke it, or for an owner or admin outside a record page, side panel, table or board, an import or a sync.

## Related documentation

- [Data model](/help/settings/data-model/index.md)
- [Pipelines](/help/settings/pipelines/index.md)
- [Custom objects](/help/custom-objects/index.md)
