Hello,
I have a column called "Income" which contains sensitive information and is accessible based on multiple business rules and custom code. We realized that while this works on the form page, any user can add the column on the list page and get to see the values.
The column permissions using object permission will also not work because as mentioned above, the field is to be made visible based on multiple rules and custom logic.
Is there a way to prevent user from adding this column on the List page?
Like
We make detail (even if there will be only one record) with records permission for such cases
Vladimir Sokolov,
That is a great idea to be sure that this value is not pulled anywhere! As of current implementation for us, we would like to retain the field at the section level and are looking for ways by which the visibility can be controlled.
I think, there has to be way for the rules on form page to reflect on the list page and in folders as well. In most cases, we hide the fields because it has information that need not be shown to some users and the platform unfortunately provides a way to by-pass this by letting users add the field on the list page.