Restricted View on Data Source

Ask the Community
,
1

Is it possible to apply a restricted view on data out of a data source?

For example we are connected to NetSuite for our accounting data, in NetSuite subsidiary specific data is restricted by the users subsidiary, but in data connection all the data is available and then we apply a restricted view at the object level.

I’m wondering if this can be done so we can build more projects faster without having to build a restricted view on all the raw datasets before building objects. Also it would be nice to apply it once at the source instead of 100 + times on every raw dataset used.

2

Hi @Nick_Mainella! I’m not sure that’s possible - so I’ll leave someone with more experience in data connections to comment on that.

However, an alternative approach we’ve done recently on a project is to “hide” all data assets in raw format (data connectors, raw data + all of the transform steps) behind a developers-only file-level marking. This prevents end-users from having access to the data if they have compass privileges and can browse through the folders.

Concepts • Markings • Palantir

Then, we set up restricted views on the final ontology-backing datasets, which are usually fewer than the number of raw data tables.

Hope this helps!

Best,

1 Like
3

That’s a good idea, we have the data source hidden/restricted to a select few but I think we can set up the raw data sources to be in a hidden project also- then only have the ‘in development’ data sets accessible to developers and apply restricted view to end users.

It’s not a bad solution since we need to stay up to date on what’s getting developed anyways, but it doesn’t restrict the data in development to the specific subsidiary’s developer. Which isn’t ideal but better than our current process.

1 Like