Hello,
I am planning to deploy a workspace with Unity Catalog enabled. Deploying permissions in one place sounds like a good solution. It can even simplify dataset architecture by masking rows and columns.
As an architect, I’m concerned about the user’s ability to include their own credentials in a shared dashboard (it’s the default behavior). By doing this, the user bypasses the permissions set at the Unity Catalog level. I think it could be really easy for a user to publish a dashboard and push its permissions without understanding the consequences.
So, I would like to disable the ability of users to include credentials in their reports.
It could also be useful to disable, for some users, the sharing dashboard functionality (for maintaining a single source of truth).
I can’t find any documentation talking about that, and it sounds really strange because I see that as a really dangerous pitfall. Am I misunderstanding something?
Regards
