# Visibility Rules **URL:** \ **Category:** Ideas & Features\ **Created:** [March 6, 2026, 12:50am UTC](https://community.fibery.io/t/visibility-rules/10499 "2026-03-06T00:50:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [March 6, 2026, 12:50am UTC](https://community.fibery.io/t/visibility-rules/10499/1 "2026-03-06T00:50:29Z")
Visibility of different pieces of functionality of Fibery (eg, buttons, etc) was discussed multiple times. I thought a concept of Visibility Rules might help. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [March 6, 2026, 6:42am UTC](https://community.fibery.io/t/visibility-rules/10499/2 "2026-03-06T06:42:43Z")
Is it the same as this: > [@Conditional fields in apps](https://community.fibery.io/t/conditional-fields-in-apps/757): > > This seems like such a no-brainer I’m wondering if somebody already asked it and I missed it (sorry if that’s the case). It would be great to have a way to make fields invisible unless another field has value X or Y, otherwise apps have a tendency to quickly get bloated. Congrats for all the good work and wish you all the best. Keep your sense of humor ? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [March 6, 2026, 6:44am UTC](https://community.fibery.io/t/visibility-rules/10499/3 "2026-03-06T06:44:54Z")
Or maybe this … > [@Turn off behaviours of Fibery app](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888): > > I really need the app stripped back to bare-bones for some users. What I would appreciate, is if admins would have privileges to change (perhaps on a per-workspace, per-database, or at the user-level access) and restrict what users can do: Disable base functionality. Sometimes it isn’t desirable, or has little use cases (and plenty of room for mistakes to occur) ‘Create new entity’ button (‘C’ shortcut) Duplicate entity Convert to Copy as markdown Hide buttons in menu All custom button a… ? ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [March 6, 2026, 8:16am UTC](https://community.fibery.io/t/visibility-rules/10499/4 "2026-03-06T08:16:32Z")
“Visibility Rules” is just an idea of a container (like Automation Rules). Yes, I think it may include button visibility rules, field visibility rules, etc.