cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

"Organization permissions" in DAB's

tedlo042034
New Contributor III

Hi all,

I've created a Databricks app in git, and it is deployed through DAB's. I want my team to have access to it and manage it and view insights and logs thus i have added in the dab CAN_MANAGE permission to my App DAB to the appropriate group.

When I deploy this app through DAB the Organization permissions gets reset. and is set to "only people with access can use"

Is there a DAB config that lets me configure this to be "Anyone in my organization can use"


1 ACCEPTED SOLUTION

Accepted Solutions

tedlo042034
New Contributor III

There appears to be a hidden group, that is not mentioned anywhere in the docs. Found by pulling the app details through databricks cli.

There is a group name "account users". If you assign CAN_USE this will allow the Organization permissions to be set to "Anyone in the Organization can view"

View solution in original post

3 REPLIES 3

tedlo042034
New Contributor III

There appears to be a hidden group, that is not mentioned anywhere in the docs. Found by pulling the app details through databricks cli.

There is a group name "account users". If you assign CAN_USE this will allow the Organization permissions to be set to "Anyone in the Organization can view"

Isaac_18
Contributor II

Nice find, and you're right. That group isn't really hidden. The Apps permissions doc says "Anyone in my organization can use" simply gives CAN USE to the All account users group, which shows up as account users when you pull the app with the CLI.

The reason it keeps resetting is that a bundle deploy sets the app's permission list to exactly what's in the bundle. Anything you toggle in the UI that isn't in the YAML gets replaced on the next deploy. So put both grants in the bundle:

resources:
  apps:
    my_app:
      name: my-app
      source_code_path: ./app
      permissions:
        - level: CAN_MANAGE
          group_name: my-team
        - level: CAN_USE
          group_name: account users

After each deploy the UI should show "Anyone in my organization can use", and your team keeps CAN MANAGE for logs and insights. Two notes from the docs: users still have to sign in through your identity provider (apps can't be made public), and if the workspace uses PrivateLink, access can fall back to workspace-level authentication.

Docs: https://docs.databricks.com/aws/en/dev-tools/databricks-apps/permissions

tedlo042034
New Contributor III

@Isaac_18 Thanks for this, that makes sense. Now I believe my confusion stems from navigating the documentation. What's the difference between azure docs and aws docs? We are hosting databricks on azure, so have been navigating the azure docs, and ignoring that in aws