Authorised views in databricks?

[Nick_Hughes]

In GCP you can give a user access to a view, and then the view itself access to the underlying object, meaning you don't have to give end users access to the tables themselves.

Is there a similar way of managing these permissions in databricks? The views would be in a different database to the underlying objects also.

[Nick_Hughes]

Hi. That isn't quite what my question was. I'm asking if I have to give users access to the tbles the view selects from too, or, if like in GCP, you can give the VIEW itself permission to the underlying objects, and then only give the user access to the view itself.

[Anonymous]

@Nick Hughes​ :

In Databricks, when you grant access to a view, it doesn't automatically grant access to the underlying tables or views. This means that you would need to explicitly grant access to the underlying tables or views in addition to granting access to the view itself.

One possible solution to avoid granting access to the underlying tables or views is to create the view in a separate database that is not accessible to end users. You can grant access to the view to the end users, but not the database that contains the underlying tables or views. This way, the end users will only be able to access the data through the view, and not directly from the underlying tables or views.

Another option is to use Row-Level Security (RLS) to filter the data that the end users can see. With RLS, you can define policies that restrict access to data based on the user's role or some other attribute. This can help you limit the data that the end users can see, without having to create separate views or databases for each user.