# Is it possible to compose a granular policy that restricts particular users from viewing a column of a particular dataset? **URL:** \ **Category:** Ask the Community\ **Tags:** pipeline-builder\ **Created:** [August 26, 2024, 4:16pm UTC](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 "2024-08-26T16:16:12Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Hirwa](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/hirwa/32/1331_2.png) [@Hirwa](https://community.palantir.com/u/Hirwa)\ **Post date:** [August 26, 2024, 4:16pm UTC](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/1 "2024-08-26T16:16:12Z")
I need to create a restricted view in my Foundry environment that prohibits a specific user or group of users from viewing a particular column in a dataset. I managed to compose a granular policy that prohibits specific users to view particular rows, but for columns I am unable to do that; so I would love to hear your thoughts on that. ---
**Author:** ![david](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@david](https://community.palantir.com/u/david)\ **Post date:** [August 26, 2024, 4:35pm UTC](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/2 "2024-08-26T16:35:41Z")
Hello and thank you for reaching out! We do not have currently have column level restricted views as a fundamental primitive throughout Foundry. There are messy ways to work around this, eg. exponentially exploding your datasets but this may be infeasible depending on the number of columns you want to be restricted. ---
**Author:** ![arnav](https://avatars.discourse-cdn.com/v4/letter/a/e68b1a/32.png) [@arnav](https://community.palantir.com/u/arnav)\ **Post date:** [August 28, 2024, 8:50pm UTC](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/3 "2024-08-28T20:50:45Z")
Another approach for implementing column-level controls is to use [Cipher](https://www.palantir.com/docs/foundry/cipher/overview/). You can [create a Cipher Channel](https://www.palantir.com/docs/foundry/cipher/getting-started/#create-a-cipher-channel) and use it to obfuscate specific columns of data with the [“Cipher Encrypt”](https://www.palantir.com/docs/foundry/cipher/apply-operations/#encryption) expression in Pipeline Builder. Only authorized users – those who have access to a Cipher License with decrypt permissions from that same Cipher Channel – will be able to de-obfuscate the data from those columns. ---
**Author:** ![jmh](https://avatars.discourse-cdn.com/v4/letter/j/e68b1a/32.png) [@jmh](https://community.palantir.com/u/jmh)\ **Post date:** [September 4, 2024, 3:33pm UTC](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/4 "2024-09-04T15:33:29Z")
You can do this for objects: https://www.palantir.com/docs/foundry/object-permissioning/multi-datasource-objects ---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [February 12, 2025, 3:35pm UTC](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/5 "2025-02-12T15:35:49Z")
Automatically bumped on February 12, 2025, 3:35pm UTC ---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [August 31, 2025, 9:18pm UTC](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/6 "2025-08-31T21:18:46Z")
Automatically bumped on August 31, 2025, 9:18pm UTC ---
**Author:** ![Acorn](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/acorn/32/5689_2.png) [@Acorn](https://community.palantir.com/u/Acorn)\ **Post date:** [September 1, 2025, 11:02am UTC](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/7 "2025-09-01T11:02:13Z")
Just to expand on what @jmh posted - For conditional visibility on dataset columns the most common Foundry pattern is probably to create an RV with only the columns to be hidden, including the PK from your original dataset. Your restricted user group won’t be able to view the data in that RV table, or view the properties it backs in downstream object types. Object types backed by multiple datasets will display only the properties from the dataset that the user has permission to view. For example, in an MDO backed by a regular dataset and an RV: ![image](https://canada1.discourse-cdn.com/palantir/original/2X/6/6bd0a8749e5f4aeaed93f8b01d065b08b1ebf2ec.png) ![image](https://canada1.discourse-cdn.com/palantir/original/2X/3/39e3e66c3844ec1e91bb628f624129def996fe9e.png) ![image](https://canada1.discourse-cdn.com/palantir/original/2X/a/ae938f9bc472ed10b4219ab34edb816701317c6c.png) The RV policy stops users from viewing certain columns (`restricted_a`, `restricted_b`). ![image](https://canada1.discourse-cdn.com/palantir/original/2X/e/eb49c57d3120cf2d3e23512dbeb5594955788982.png) General reminder that permissions should be established as far upstream as possible, instead of being bolted on later. I’d suggest you configure the markings on the original data source project to exclude the users whose view you want to restrict. Then, if you’d like that data to be more widely viewable, you can create RVs or purposefully strip out the marking from column subsets of that dataset.