# Turn off behaviours of Fibery app **URL:** \ **Category:** Ideas & Features\ **Created:** [October 27, 2025, 12:12am UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888 "2025-10-27T00:12:30Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [October 27, 2025, 12:12am UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/1 "2025-10-27T00:12:30Z")
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: 1. 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 1. Hide buttons in menu - All custom button actions appear on the right-click of an entity and in the entity actions menu. There are use cases where these buttons should be only visible/accessible in certain situations and to certain people/access levels. I know this is a big ask (indicated by what @Chr1sG said here) > [@Separate permission for buttons and workflows](https://community.fibery.io/t/separate-permission-for-buttons-and-workflows/8350/2): > > …field-level permissions in general, which is something that is not on the radar, due to the complexity. I know “this could all be avoided with training”, but I feel like Sisyphus with how much 💩 I’m pushing uphill just to get our users to log stuff in the app ---
**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:** [November 6, 2025, 7:21am UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/2 "2025-11-06T07:21:52Z")
Entity actions and bulk entity actions are being added to more and more, pushing our custom made buttons down the menu, of even off the bulk selector. Having a section for “Defaults” in database button settings, (Edit Fields, Convert to, Duplicate, Download Files, Merge Into, Copy as Markdown, Delete), with the ability to turn each on or off by the Architect would be fantastic! ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [November 6, 2025, 7:25am UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/3 "2025-11-06T07:25:50Z")
I suggested a week ago, for different reason. > [@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… Technophobes are confused. ---
**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:** [November 6, 2025, 8:18am UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/4 "2025-11-06T08:18:20Z")
Yup! I’d like to make the request more specific be changing the name to “Control what action/buttons are visible in entity menu, right click, and bulk actions. (Default and User Created)” But this does not encompass disabling the “C” to create. What do you think? ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [November 6, 2025, 9:11pm UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/5 "2025-11-06T21:11:41Z")
“C” to create would not be such a bad thing if all the forms could be set. Atm it seems to just fall back to the default. ---
**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:** [November 6, 2025, 11:33pm UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/6 "2025-11-06T23:33:22Z")
Mind if we rename this topic to be just around buttons (user and default), and you make a new topic around the “C” to create problems? Just keeps things more specific and clear what people can vote for. ---
**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:** [November 7, 2025, 12:15pm UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/7 "2025-11-07T12:15:28Z")
I think so long as there aren’t dozens of votes for this topic, it’s OK for it to be an umbrella. ---
**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:** [November 7, 2025, 12:16pm UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/8 "2025-11-07T12:16:30Z")
[Related](https://community.fibery.io/t/button-group-dropdown-field/6396) ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [October 8, 2026, 5:35am UTC](https://community.fibery.io/t/turn-off-behaviours-of-fibery-app/9888/9 "2026-10-08T05:35:03Z")
Sorry to necro, but this is still very relevant to me, and a huge reason why I can’t implement better workflows for users. …bump