# \[DONE\] Validations / automations **URL:** \ **Category:** Ideas & Features\ **Created:** [October 16, 2024, 2:35pm UTC](https://community.fibery.io/t/done-validations-automations/7584 "2024-10-16T14:35:06Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Nevil\_Hulspas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nevil_hulspas/32/4703_2.png) [@Nevil\_Hulspas](https://community.fibery.io/u/Nevil_Hulspas)\ **Post date:** [October 16, 2024, 2:35pm UTC](https://community.fibery.io/t/done-validations-automations/7584/1 "2024-10-16T14:35:06Z")
Just saw the monthly update from @mdubakov and it inspired this feature request. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4d4bf03f9791e501f71c20677c2affa44ff3fe51.jpeg) The required fields (above) is a good first step in what we’re missing in our workspace, which is what I would call validations. Validation is where a user is not allowed to take certain actions unless another condition is fulfilled. A few examples: - Only allow updating to state “done” when “rich text” field is not empty. - Only allow creating a todo if the deadline is also entered - When disapproving something (state = disapproved), a text modal appears where you need to state the reason why it’s disapproved. - Forcing certain items to be marked as done in a certain order. Ideal for checklists, where you want somebody not to finish task 2 before task 1 is done. - Only certain permission groups are allowed to update the budget field of a project Some of these things are already possible with a bit of workaround, as @ChrisG already greatly helped us with. But would be ideal if this was natively possible, on a per-field basis. It probably intertwines quite a bit with permissions and automations, and maybe most of this is already possible, but I felt it deserved it’s own thing. ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [October 18, 2024, 8:58am UTC](https://community.fibery.io/t/done-validations-automations/7584/2 "2024-10-18T08:58:40Z")
I also would like to see the integration of Conditions. I don’t know if adding that at a Field level is the best solution but at least if it can be added in Automation, this will already be a good step forward in my opinion. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 23, 2025, 1:28pm UTC](https://community.fibery.io/t/done-validations-automations/7584/3 "2025-12-23T13:28:09Z")
Validation Rules development started ---
**Author:** ![Dev](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@Dev](https://community.fibery.io/u/Dev)\ **Post date:** [September 8, 2022, 7:01pm UTC](https://community.fibery.io/t/done-validations-automations/7584/4 "2022-09-08T19:01:10Z")
Hi Fibery, So far I’ve seen alot of great things in Fibery, but a big blocker for me actual moving company data inside is the lack of field validation and unique fields. I need the ability to make any field I create unique, so that an error pops up or I’m simply unable to input a new row if that field is a duplicate. I also need the ability to do more complex field validation, such as field A can’t be x when field B is y. Without these things there’s a very big risk of data duplication and errors. Thanks and great job so far with this tool! ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [September 8, 2022, 11:40pm UTC](https://community.fibery.io/t/done-validations-automations/7584/5 "2022-09-08T23:40:12Z")
If you search this forum for “unique” you will find that there has been some discussion on this topic, including some ways to enforce/warn about uniqueness violations. ---
**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\ **Post date:** [February 27, 2025, 2:20pm UTC](https://community.fibery.io/t/done-validations-automations/7584/6 "2025-02-27T14:20:10Z")
Unique fields and fields validation (via formulas for example) would be great 👍 ---
**Author:** ![Konstantin\_Trunin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/konstantin_trunin/32/829_2.png) [@Konstantin\_Trunin](https://community.fibery.io/u/Konstantin_Trunin)\ **Post date:** [July 17, 2020, 7:10pm UTC](https://community.fibery.io/t/done-validations-automations/7584/7 "2020-07-17T19:10:22Z")
Hello. I can’t find this in examples and settings - please help. I want to implement validation when entering new row into a table: e.g. IF field A is OPTION1 then field B and C should be not empty, IF field A is OPTION2 then field D and F should be not empty, and so on. Is it somehow possible? If not - can I at least have formula that will do the same and if it is FALSE displays ERROR label/text? ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [July 21, 2020, 8:35pm UTC](https://community.fibery.io/t/done-validations-automations/7584/8 "2020-07-21T20:35:53Z")
Hi, Konstantin 🙂 We would suggest boolean formula (checkbox) and color-coding on top There is no need in the If formula - just a combination of `and`/`or` showing `boolean` Btw, if you could share with us your case with details, there is a chance, that we can find a better solution 😉 ---
**Author:** ![Konstantin\_Trunin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/konstantin_trunin/32/829_2.png) [@Konstantin\_Trunin](https://community.fibery.io/u/Konstantin_Trunin)\ **Post date:** [July 22, 2020, 8:14am UTC](https://community.fibery.io/t/done-validations-automations/7584/9 "2020-07-22T08:14:31Z")
re: Btw, if you could share with us your case with details, there is a chance, that we can find a better solution Validation is important part of ANY workflow. Some examples: - allow only tasks with Estimate be scheduled. - allow only tasks with Estimate and Scheduled to be worked on and receive work logs - allow only correct financial transaction with all required fields to be created etc ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [January 9, 2026, 12:41pm UTC](https://community.fibery.io/t/done-validations-automations/7584/10 "2026-01-09T12:41:35Z")
Some update of validation rules development https://www.loom.com/embed/344343814e97494eaca80864c93e75cb ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [January 9, 2026, 1:30pm UTC](https://community.fibery.io/t/done-validations-automations/7584/11 "2026-01-09T13:30:52Z")
Hey! Quick question: This looks very similar to automations. When “Previous Value” is released, what would be the difference between validation vs an automation that checks for update, has conditions and then sets the field to its previous value if the conditions are true? From my understanding: 1. [The error message showing.](https://community.fibery.io/t/show-toast-through-rule-automations/9468) 2. [Ability to set validation/filters using formula (rules only use the no-code filters)](https://community.fibery.io/t/to-be-able-to-use-formula-in-automation-filters/3706) I would love to see these things in rules as opposed to a separate tab. But of course, I might be missing something. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [January 9, 2026, 1:57pm UTC](https://community.fibery.io/t/done-validations-automations/7584/12 "2026-01-09T13:57:35Z")
Background mechanism is fundamentally different. Automation Rule triggers when a change already happened, while Validation rule prevents the change itself. So with your workaround you will see two changes in history (the change itself and reverted back by automation rule), while with Validation rule there will be nothing in changes history ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [January 9, 2026, 2:12pm UTC](https://community.fibery.io/t/done-validations-automations/7584/13 "2026-01-09T14:12:18Z")
Ahh thats fantastic! Thought I might be missing something. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [January 15, 2026, 12:33pm UTC](https://community.fibery.io/t/done-validations-automations/7584/14 "2026-01-15T12:33:31Z")
First release is done today > [@January 15, 2026 / police\_officer Validation rules, New Connector styles and options, “Periods” integration](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247): > > police_officer Validation rules Today we’re introducing new concept in Fibery — Validation Rules. Validation Rules in Fibery help keep your data accurate and consistent. Think of a validation rule as a bouncer at a club door smiling_face_with_sunglasses. Before any data change gets in, the bouncer checks: “Does this meet our standards?” If not, the change is blocked and the user gets a friendly explanation of what’s wrong. A validation rule fires when its condition is true, and it blocks th… ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [January 22, 2026, 3:34pm UTC](https://community.fibery.io/t/done-validations-automations/7584/15 "2026-01-22T15:34:28Z")
Second release with more use cases covered > [@January 22, 2026 / 🎛️ Architect mode, many AI and validation rules improvements](https://community.fibery.io/t/january-22-2026-architect-mode-many-ai-and-validation-rules-improvements/10284): > > control_knobs Architect vs. User modes Today we’re introducing a new way to keep Fibery calm and safe for everyday work: Architect vs. User modes. Admins and Architects can now switch between two modes: User mode: a cleaner, focused interface for daily work. Advanced controls are hidden: no accidental field edits, no surprise layout changes, fewer dangerous actions like Delete Relation Field in your face. Architect mode: the full power view for workspace design. Architect mode can be … ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [March 4, 2026, 12:32pm UTC](https://community.fibery.io/t/done-validations-automations/7584/16 "2026-03-04T12:32:48Z")
3 posts were split to a new topic: [Validation Rules that just show warning and do not block action](https://community.fibery.io/t/validation-rules-that-just-show-warning-and-do-not-block-action/10488) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [July 6, 2026, 5:06am UTC](https://community.fibery.io/t/done-validations-automations/7584/17 "2026-07-06T05:06:00Z")