topic Granting Permission on Notification Destinations in Data Governance

Granting Permission on Notification Destinations

Michael_Appiah — Thu, 22 Aug 2024 14:46:24 GMT

We are trying to add Slack as a "Notification destination" under "Workspace Settings" in our Databricks workspace.

However, there is no option to actually grant permission on that destination to define who gets to actually use that destination. This is an issue when using Slack as notification destination.

We want to make sure that only the team who owns that particular Slack Channel gets to set that Slack Channel as their destination. Other teams should not have the option to use that Slack destination.

However, there does not seem to be a way to set permissions on notification destinations - or am I missing something here?

Re: Granting Permission on Notification Destinations

emmalily — Sat, 31 Aug 2024 11:09:36 GMT

Hi,

Databricks doesn't allow direct permissions management for Slack notification destinations. To control access:

Create Private Channels: Use private Slack channels for notifications and only add relevant team members.
Manage Roles: Use Databricks role-based access controls to limit who can configure workspace settings.
Custom Solutions: Consider using APIs for more detailed control if needed.

If you need more specific features, contacting Databricks support might help.

Best regards.

Emma lily

Re: Granting Permission on Notification Destinations

Michael_Appiah — Sat, 30 Nov 2024 19:21:57 GMT

Hi @emmalily ,

thanks for your answer. I am curious to hear more about your first proposed solution "creating private channels". I am not sure how that would prevent others from using the Slack notification destination since everyone in the Databricks workspace could set that destination e.g. in their jobs. Could you elaborate on how referencing a private Slack channel (since its just a url) in the notification settings in Databricks prevents others from using that destination?