I have a dataset called ‘tb_accounts’ (example) and I was able to apply row-level security to it, but how can I block users from creating new datasets from the ‘tb_accounts’ glue table and avoid using my secured dataset?
Hello @Pedrosa, do the users need access to the data source for other functionalities? The easiest option would be to not give users access to the data source and only share datasets with them as users rather than owners. That would ensure they are unable to make any queries against the glue table and they would not be able to edit the dataset.
Alternatively, if they need some permissions to the glue table but not others, then you would have to get more granular with their policy and specifically identify the resources that they can access and edit. Here is some documentation on that process:
The 2nd option is definitely more complicated, so if the first option can be utilized, that would be ideal.