Hello @Simon I require your assistance with a specific use case. Suppose I create a view using the `%sql` declaration with the `CREATE OR REPLACE VIEW` statement and grant the Databricks group 'X' usage access to the schema and catalog, along with select access to the view. Consequently, a user who is a member of the Databricks group 'X' will gain visibility of the object and the ability to retrieve data from the view. However, a challenge arises when I execute the `CREATE OR REPLACE VIEW` statement again. It appears that the previously granted permissions for Databricks group 'X' vanish, subsequently restricting users in that group from accessing the object. Could you please provide guidance /feedback on this ? Your assistance is greatly appreciated.
Currently, Would it even be possible to a bit of both, .i.e. Row based masking a column. Ex: Hide the phone number/email if the person is not an admin.