It is not possible to prevent base collaborators from viewing certain fields (columns) within a table or base. To get around this problem, the only recommended solution I have seen in this community is third-party tools, also referred to as external tools or portal tools.
Examples of these recommended tools are Noloco.io, MiniExtensions.com, GlideApps.com, Softr.io, Pory.io, and StackerHQ.com.
But rather than using a third-party tool, what if we created a “mirror base” within AirTable, and established a different set of collaborators for the mirror base?
The mirror base would be a duplicate of the original base, but with several additional fields added. The mirror would update in real time whenever the original base is updated. The two bases would always be exact copies of each other, except that the mirror would have several additional fields.
Could this work?