@antoniokov fair points all, check them out
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.
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(!)
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ā?
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?
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.
100% agree. Scripts are the only reason theyāre Admins in the first place, so really looking forward to non-Admin scripts!
![]()