# Granular AI Access Control (Space-level AI Permissions) **URL:** \ **Category:** Ideas & Features\ **Tags:** ai\ **Created:** [March 17, 2026, 7:53am UTC](https://community.fibery.io/t/granular-ai-access-control-space-level-ai-permissions/10580 "2026-03-17T07:53:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ID.000](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/id.000/32/14109_2.png) [@ID.000](https://community.fibery.io/u/ID.000)\ **Post date:** [March 17, 2026, 7:53am UTC](https://community.fibery.io/t/granular-ai-access-control-space-level-ai-permissions/10580/1 "2026-03-17T07:53:07Z")
Hi Fibery team! I’d like to share a thought on how to make Fibery AI more “Management-friendly,” especially for larger organizations. It would be great to have the ability to restrict Fibery AI access to specific Spaces. For example, if a company has a Space with sensitive financial data and another one for general tasks, management would feel much more comfortable enabling AI for the entire account if they could simply ‘switch it off’ for the finance-related Space. This would give leadership peace of mind while still allowing the team to use AI for their daily work. Thank you 🙂 ---
**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 17, 2026, 7:54am UTC](https://community.fibery.io/t/granular-ai-access-control-space-level-ai-permissions/10580/2 "2026-03-17T07:54:42Z")
Good idea, we will see how to do it ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [March 17, 2026, 8:00am UTC](https://community.fibery.io/t/granular-ai-access-control-space-level-ai-permissions/10580/3 "2026-03-17T08:00:48Z")
I wonder if there’s a way to segment AI usage for “global databases”. For example, a global documents database might be used for an organizational wiki, but it also might be used for some secure information. I don’t know if it would be possible to give AI access to the former but not for the latter. ---
**Author:** ![ID.000](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/id.000/32/14109_2.png) [@ID.000](https://community.fibery.io/u/ID.000)\ **Post date:** [March 17, 2026, 8:03am UTC](https://community.fibery.io/t/granular-ai-access-control-space-level-ai-permissions/10580/4 "2026-03-17T08:03:12Z")
Thank you very much 🙂 ---
**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 17, 2026, 10:28am UTC](https://community.fibery.io/t/granular-ai-access-control-space-level-ai-permissions/10580/5 "2026-03-17T10:28:03Z")
I think we should consider introducing the concept of AI agents as additional users in the workspace, potentially each under control of a human user. In other words, admins/architects can define what access each (human) user is allowed, and then any user can create ‘delegate AI’ users. By default, the AI users get the the same permissions as their human master, but the user also has the option of restricting them, e.g. making one of their AI delegates a read-only agent, making another limited to certain spaces/dbs, another limited to certain entities etc. Hopefully, the AI providers (openai, anthropic etc.) will make it easy for users to interact with external tools (like Fibery) via multiple ‘personas’ instead of always granting the same permission level for every interaction