# January 15, 2026 / 👮 Validation rules, New Connector styles and options, “Periods” integration

**URL:** <https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247>\
**Category:** Changelog\
**Created:** [January 15, 2026, 12:00pm UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247 "2026-01-15T12:00:31Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [January 15, 2026, 8:04pm UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/17 "2026-01-15T20:04:42Z")

</div>

Validation Rules look awesome. I love this direction for Fibery. A few early observations and opportunities:

* * *

**Field-Level Permissions**  
Because validation rules can reference the **User** , they appear to enable a workaround for field-level permissions (e.g., blocking edits for certain users). Not sure if this is intentional, but it’s a powerful capability.

* * *

**UI Enhancement to Fields**  
Validation rules (and other rules) should be visible in the settings of the fields they reference. This would improve discoverability and reduce the risk of breaking logic when editing fields. [Show and Manage Rules in Field Settings (UI Enhancement)](https://community.fibery.io/t/show-and-manage-rules-in-field-settings-ui-enhancement/10250)

* * *

**Conditionally Required Fields**  
Validation rules move Fibery closer to conditionally required fields but stop short. [Conditional Required Fields - Workflow validation](https://community.fibery.io/t/conditional-required-fields-workflow-validation/9268)

Ideally there would be a way to prompt a user to correct the failed validation, the value being that the system now encourages users to correct the data entry instead of just blocking changes.

Use case:

- A user updates a field (e.g., Opportunity → State = “Lost”).
- Validation fails because another field required for that state is empty.
- In addition or instead of the Validation Error Message, Fibery prompts the user to fix the missing field or cancel the change (reverting the original update).

---

_[View the full topic](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247)._