Create and manage rules
Set rules that control how records can be updated.
Available on pro and enterprise plans.
Admins can create and manage rules.
Members can create and manage rules with Full access to the relevant object.
On the Pro plan, admins can create up to three rules per object. There is no limit on the Enterprise plan.
Rules let you control when changes to records can be saved. Each rule has a condition that determines when it applies and one or more requirements that must be met. If the condition is met but a requirement isn't, Attio blocks the change.
For example, you can require Deal value before a deal moves to Won, or require Lost reason before it moves to Lost.
Rules are checked when records are created or updated.
Create a rule
Rules are created for individual objects. For example, a rule you create on Deals applies to deal records only. Rules aren't available on lists.
Click your workspace name, then select Workspace settings.
Under Data, click Objects, then select the object you want to add a rule to.
Open the Rules tab.
Click + Add.
Enter a name for the rule.
Set the Condition that determines when the rule applies.
Add one or more Requirements that must be met.
Optionally, click + Actor under Applies to to limit the rule to specific members or teams.
Click Save.
Your rule takes effect immediately and appears in the table on the Rules tab. It doesn't modify existing records.
Name
The name identifies the rule in the table on the Rules tab. Names that describe the outcome are easiest to scan later, such as "Require Deal value when deal is Won”.
Condition
The condition determines when the rule applies. Build it the same way you build a view filter by choosing an attribute, operator, and value. For example, Deal stage > is > Won.
Click the + icon to add another condition, or select the ⋮ icon to the right of a condition and select Convert to advanced condition. From there you can also create a filter group to nest conditions with 'and/or' modifiers.
Requirements
Requirements define what must be true when the rule's condition is met. Choose an attribute, then select an option:
is required: The attribute must have a value.
must be empty: The attribute must not have a value.
For number, currency, rating, date, and timestamp attributes, you can also compare the attribute against a value you set:
greater than: The value must be higher than the one you set.
at least: The value must be equal to or higher than the one you set.
less than: The value must be lower than the one you set.
at most: The value must be equal to or lower than the one you set.
equals: The value must match the one you set.
For select, pipeline, text, and checkbox attributes, and for attributes that reference a record or a workspace member, you can require a specific value:
equals: The attribute must be set to the value you choose.
You can't set a requirement on an AI-generated attribute or a formula attribute.
Click the + icon next to Requirements to add another requirement. To remove one, click the ⋮ icon on the requirement and select Delete.
Applies to
By default, a rule applies to changes made by anyone. Use Applies to to limit the rule to changes made by specific members or teams.
Click + Actor, then choose Members, Teams, or Workflows, and search for the ones you want. Add more than one by clicking the + again.
Edit or delete a rule
Existing rules appear in a table on the Rules tab, showing each rule's name and who or what it applies to.
Click the ⋮ icon to the right of the rule you want to change.
Select Edit to open the rule and make changes, or Delete to remove it.
Deleting a rule stops Attio from enforcing it, and changes that it previously blocked can be saved again.
When a rule blocks a change
If a change meets a rule’s condition but doesn’t meet its requirements, Attio blocks the change. When editing a record in Attio, an Updates required dialog opens showing the change that triggered the rule and the attributes that need values.
Fill in the required values, then click Save. Attio saves your original change along with the values you added. If a value you enter triggers another rule, the dialog refreshes to show the additional attributes you need to fill in. Closing the dialog without saving discards the change.
Rules apply to any change you make yourself, wherever you make it. That includes the Attio web app, the mobile app, CSV imports, Ask Attio, and through the Attio MCP.
CSV imports: If a row doesn't meet a rule's requirements, that row isn't imported. It shows as Failed with the error "Blocked due to object rules violation."
Ask Attio: The attributes the rule requires are added to the approval card. Set the values and click Update to apply all the changes together, or click Discard all to cancel.
Workflows: If a block tries to make a change that a rule blocks, the block fails. Open the run and select the failed block to see the reason. Learn more about troubleshooting workflows.
Rules don't apply to changes Attio makes on its own. This includes enrichment, email and calendar sync, the interaction attributes Attio maintains such as First interaction and Last interaction, records created automatically from email and calendar activity, and data brought in by Import2. Rules also don’t currently apply to the Attio API, apps, or integrations.
Records that already break a rule
Creating a rule doesn’t change or flag existing records that don’t meet its requirements.
The next time one of those records is edited, the rule is checked. The change can’t be saved until the record meets the rule’s requirements, even if the attribute being edited isn’t part of the rule.
For example, if Deal value is required when Deal stage is Won, changing the name of an existing won deal with no Deal value prompts you to add Deal value before the change can be saved.
Related resources
Learn more about creating and managing attributes and managing access to objects.
Frequently asked questions
A required attribute must always have a value when a record is created. Required attributes are only supported on custom objects.
A rule makes an attribute required only when specific conditions are met. For example, you can require Deal value only when Deal stage is Won. Rules can be created for any object.
No, rules apply to attribute values when a record is created or updated.