How to Implement Column-Level Security in Palantir Foundry?

Ask the Community
1

Hey folks,

I’m working on a data governance use case in Foundry, and I’m trying to figure out the best way to implement column-level security. Specifically, I want to:

  • Restrict access to certain sensitive columns (like PII or financial data) based on user roles or groups.
  • Allow access to the rest of the dataset without duplicating or splitting the dataset manually.
  • Ensure this works seamlessly across downstream tools like Code Workbooks, Contour, or Slate apps.

I’ve read about Markings, object-level access, and scoped sessions, but I’m not clear on how (or if) column-level control can be handled natively in the platform. Is this possible via ontology, transforms, or some other Foundry-native feature?

Would love to hear how others are handling this in real-world projects.
Any best practices, documentation links, or hacks are welcome!

Thanks in advance. :raising_hands:

2 Likes
2

hey roushan.

thanks for the question. unfortunately at time of writing, the only solution is to use multiple backing datasets. this will probably have to involve some splitting of the dataset as you list in your second point.

1 Like
3

Hey - read similar query in different thread as well. check once and give a try

https://community.palantir.com/t/is-it-possible-to-compose-a-granular-policy-that-restricts-particular-users-from-viewing-a-column-of-a-particular-dataset/1147