# October 8, 2026 / đŸ«Ł Hide Space data from Admins **URL:** \ **Category:** Changelog\ **Created:** [October 8, 2026, 1:10pm UTC](https://community.fibery.io/t/october-8-2026-hide-space-data-from-admins/11389 "2026-10-08T13:10:13Z")\ **Posts on this page:** 4\ **Page:** 2
**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:** [October 15, 2026, 1:20pm UTC](https://community.fibery.io/t/october-8-2026-hide-space-data-from-admins/11389/21 "2026-10-15T13:20:45Z")
@antoniokov fair points all, check them out ---
**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:** [October 15, 2026, 1:49pm UTC](https://community.fibery.io/t/october-8-2026-hide-space-data-from-admins/11389/22 "2026-10-15T13:49:38Z")
> [@Artur](#): > > Two things. First, wiki docs: a Document view is the content itself (payment setup, tax and banking notes, salary policy), not “how the tool works”, and Admins can still read it. I would suggest not using Documents (views) for content which you want to be access-controlled. Use a Document database (with a rich text field) and configure the access so that only people who need to can see the entities. > [@Artur](#): > > Say performance review is built as a Custom App. The rating scale, the bonus multiplier for each rating and the promotion criteria live in the app itself, not in rows. Are you saying that there are formulas whose mere existence (how they are calculated) reveals ‘sensitive’ information, which should not necessarily be accessible to Admins? If an employee is given a rating score (which the Admin does not see) surely it’s ok for everyone to know what the rating scale is, otherwise you would be saying that “You have been given a score of 3.5” but not telling them if it is out of 5 or out of 10(!) > [@Artur](#): > > Calibration also has a “Planned exit” option, and there’s a view for the Q1 restructuring. Not sure I get this. Are you saying that there is a select field called ‘Calibration’ with one of the options being ‘Planned exit’ ? Or that there is a view called ‘Q1 restructuring’? > [@Artur](#): > > The Admin who needs scripts is often a technical hire or a consultant, trusted to build but not to see every department. So for some Spaces it has to be “you have it or you don’t”. Allowing non-admins to write scripts is on the radar, but that’s an independent issue to the one of whether or not the schema/configuration itself reveals ‘sensitive’ info, no? ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [October 15, 2026, 3:05pm UTC](https://community.fibery.io/t/october-8-2026-hide-space-data-from-admins/11389/23 "2026-10-15T15:05:51Z")
These are pretty reasonable expectations in your case. And in your scenario I think a better way to deal with them is to not have such Admins in the first place. I hope we can unlock scripts for non-Admins in the coming months. ---
**Author:** ![Artur](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/artur/32/13768_2.png) [@Artur](https://community.fibery.io/u/Artur)\ **Post date:** [October 17, 2026, 3:58pm UTC](https://community.fibery.io/t/october-8-2026-hide-space-data-from-admins/11389/24 "2026-10-17T15:58:27Z")
100% agree. Scripts are the only reason they’re Admins in the first place, so really looking forward to non-Admin scripts! 💓 đŸ€Ÿ [Previous page](https://community.fibery.io/t/october-8-2026-hide-space-data-from-admins/11389.md?page=1)