I need a way to hash a specific cell of the dataset, if the user is from a country who is not allowed to see it?

Ask the Community
1

Is there a way to make this possible?

2

Can you just use a restricted view and restrict access to that specific column? https://www.palantir.com/docs/foundry/security/restricted-views/#restricted-views

3

Is it possible to restrict views for a single cell? Beacuse i dont want to restrict a whole column or row

4

Basically, 3 big ways I can immediately think of:

Restricted Views and MDO

Restricted Views and MDO are ways to limit which rows/columns users can see. Or the user will see the column/row, or they won’t see it. No middle ground (e.g. cell level).
Given permissioning of object instances is directed by dataset-access, this is covered in two folds:

  • Restricted Views which limits which rows can be seen
  • MDO ( Multi dataset backed object) which limits which set of columns can be seen, but storing the dataset/RV in a separate project where only a bunch of users can see it.

For example, in the below scenario, users that have access to Project A, can see the columns A,B,C. Users that can access project B can see columns D,E,F. Users as specified in the restricted view will be able to see rows they are entitled to see.

image
image2486×1512 141 KB

Cipher

This allow for cell-level conditional access. For example “this user can see this cell, but only if they meet specific condition. Or they can access only a limited number of cells per day for their workflows, e.g. 10”.
The idea is to cipher (encrypt/hash/…) the values of specific columns and grant the permission to decipher to specific users under specific conditions.

This is likely the closest from your ask.

Policy Security Groups

That’s basically the “newer version” of the MDO and Restricted Views setup, for objects. (Restricted views are still the way to go for dataset level row-level access).
It simplifies the setup by letting you configure the row/columns access directly in the Ontology.