Skip to main content

Access control lists

This page describes details about the permissions available for the different workspace objects.

Access control lists overview

In Databricks, you can use access control lists (ACLs) to configure permission to access workspace level objects. Workspace admins have the CAN MANAGE permission on all objects in their workspace, which gives them the ability to manage permissions on all objects in their workspaces. Users automatically have the CAN MANAGE permission for objects that they create.

For an example of how to map typical personas to workspace-level permissions, see the Proposal for Getting Started With Databricks Groups and Permissions.

Manage access control lists with folders

You can manage workspace object permissions by adding objects to folders. Objects in a folder inherit all permissions settings of that folder. For example, a user that has the CAN RUN permission on a folder has CAN RUN permission on the alerts in that folder.

If you grant a user access to an object inside the folder, they can view the parent folder's name, even if they do not have permissions on the parent folder. For example, a notebook named test1.py is in a folder named Workflows. If you grant a user CAN VIEW on test1.py and no permissions on Workflows, the user can see that the parent folder is named Workflows. The user cannot view or access any other objects in the Workflows folder unless they have been granted permissions on them.

To learn about organizing objects into folders, see Workspace browser.

Alerts ACLs

Ability

NO PERMISSIONS

CAN RUN

CAN MANAGE

See in alert list

View alert and result

Manually trigger alert run

Subscribe to notifications

Edit alert

Modify permissions

Delete alert

Compute ACLs

important

On compute resources that use the legacy access mode No isolation shared, users with CAN ATTACH TO permissions can view the service account keys in the log4j file. Use caution when granting this permission. For more detail on this mode and how to restrict it, see What are no isolation shared clusters?.

Ability

NO PERMISSIONS

CAN ATTACH TO

CAN RESTART

CAN MANAGE

Attach notebook to compute

View Spark UI

View compute metrics

Terminate compute

Start and restart compute

View driver logs

(see note)

Edit compute

Attach library to compute

Resize compute

Modify permissions

note

Secrets are not redacted from a cluster's Spark driver log stdout and stderr streams. To protect sensitive data, by default, Spark driver logs are viewable only by users with CAN MANAGE permission on job, dedicated access mode, and standard access mode clusters. To allow users with CAN ATTACH TO or CAN RESTART permission to view the logs on these clusters, set the following Spark configuration property in the cluster configuration: spark.databricks.acl.needAdminPermissionToViewLogs false.

On No Isolation Shared access mode clusters, the Spark driver logs can be viewed by users with CAN ATTACH TO, CAN RESTART, or CAN MANAGE permission. To limit who can read the logs to only users with the CAN MANAGE permission, set spark.databricks.acl.needAdminPermissionToViewLogs to true.

See Spark configuration to learn how to add Spark properties to a cluster configuration.

Dashboard ACLs

Ability

NO PERMISSIONS

CAN VIEW/CAN RUN

CAN EDIT

CAN MANAGE

View dashboard, results, and datasets

Interact with widgets

Refresh the dashboard

Edit dashboard

Clone dashboard

Publish dashboard snapshot

Modify permissions

Delete dashboard

Legacy dashboard ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN RUN

CAN EDIT

CAN MANAGE

See in dashboard list

View dashboard and results

Refresh query results in the dashboard (or choose different parameters)

Edit dashboard

Modify permissions

Delete dashboard

Editing a legacy dashboard requires the Run as viewer sharing setting. See Refresh behavior and execution context.

Database instance ACLs

Ability

NO PERMISSIONS

CAN CREATE

CAN USE

CAN MANAGE

Get database instance

List database instances

Create database instance

Create synced table

Create Unity Catalog database catalog

Modify Postgres roles

Delete database instance

Modify permissions

Pause database instance

Resume database instance

note
  • All workspace users automatically inherit CAN CREATE permission. This permission cannot be assigned or removed.
  • When performing operations that interact with Unity Catalog you need to have permissions on the Unity Catalog object:
    • Create Unity Catalog database catalog: Requires the CREATE CATALOG privilege on the Unity Catalog metastore.
    • Create synced table: Requires Unity Catalog permissions to read the source table, write to the destination schema, and write to the pipeline storage schema.

Lakebase project ACLs

These ACL tables show permissions for Lakebase (Autoscaling) projects. For Lakebase (Provisioned) permissions, see Database instance ACLs.

For more information about Lakebase (Autoscaling), see Projects.

note
  • Workspace admins automatically inherit the CAN MANAGE permission on all Lakebase project resources.
  • All workspace users automatically inherit the CAN CREATE permission. This permission cannot be assigned or removed.
  • To grant access to other individuals, groups, or service principals, assign the CAN MANAGE permission.

Project ACLs

Ability

NO PERMISSIONS

CAN CREATE

CAN MANAGE

View project

Create project

Delete project

Update project

View connection URI

List projects

View project limits

Branch ACLs

Ability

NO PERMISSIONS

CAN CREATE

CAN MANAGE

List project branches

Create project branch

Count project branches

Create branch database

Create branch role

Delete project branch

Delete branch database

Delete branch role

Delete project branches

Finalize restore branch

View project branch

View branch database

View branch role

View branch role password

View branch schema

List branch databases

List branch endpoints

List branch roles

Reset project branch

Reset branch role password

Reset branch to parent

Restore project branch

Set default project branch

Update project branch

Update branch database

Snapshot ACLs

Ability

NO PERMISSIONS

CAN CREATE

CAN MANAGE

List snapshots

Create snapshot

View snapshot schedule

Set snapshot schedule

Delete snapshot

Update snapshot

Restore snapshot

Endpoint ACLs

Ability

NO PERMISSIONS

CAN CREATE

CAN MANAGE

List project endpoints

Create project endpoint

Delete project endpoint

View project endpoint

Restart project endpoint

Start project endpoint

Suspend project endpoint

Update project endpoint

Operation ACLs

Ability

NO PERMISSIONS

CAN CREATE

CAN MANAGE

View project operations

List project operations

List running project operations

Lakeflow Spark Declarative Pipelines ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN RUN

CAN MANAGE

IS OWNER

View pipeline details and list pipeline

View Spark UI and driver logs

Start and stop a pipeline update

Stop pipeline clusters directly

Edit pipeline settings

Delete the pipeline

Purge runs and experiments

Modify permissions

Feature tables ACLs

This table describes how to control access to feature tables in workspaces that are not enabled for Unity Catalog. If your workspace is enabled for Unity Catalog, use Unity Catalog privileges instead.

note

Ability

CAN VIEW METADATA

CAN EDIT METADATA

CAN MANAGE

Read feature table

Search feature table

Publish feature table to online store

Write features to feature table

Update description of feature table

Modify permissions

Delete feature table

File ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN RUN

CAN EDIT

CAN MANAGE

Read file

Comment

Attach and detach file

Run file interactively

Edit file

Modify permissions

note

The workspace UI refers to view-only access as CAN VIEW, while the Permissions API uses CAN READ to represent the same level of access.

Folder ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN EDIT

CAN RUN

CAN MANAGE

List objects in folder

View objects in folder

Clone and export items

Run objects in the folder

Create, import, and delete items

Move and rename items

Modify permissions

note

The workspace UI refers to view-only access as CAN VIEW, while the Permissions API uses CAN READ to represent the same level of access.

Genie space ACLs

Ability

NO PERMISSIONS

CAN VIEW/CAN RUN

CAN EDIT

CAN MANAGE

See in Genie space list

Ask Genie questions

Provide response feedback

Add or edit Genie instructions

Add or edit sample questions

Add or remove included tables

Monitor a space

Modify permissions

Delete space

View other users' conversations

Git folder ACLs

Ability

NO PERMISSIONS

CAN READ

CAN RUN

CAN EDIT

CAN MANAGE

List assets in a folder

View assets in a folder

Clone and export assets

Run executable assets in folder

Edit and rename assets in a folder

Create a branch in a folder

Switch branches in a folder

Pull or push a branch into a folder

Create, import, delete, and move assets

Modify permissions

Job ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN MANAGE RUN

IS OWNER

CAN MANAGE

View job details and settings

View results

View Spark UI, logs of a job run

Run now

Cancel run

Edit job settings

Delete job

Modify permissions

note
  • The creator of a job has the IS OWNER permission by default.

  • A job cannot have more than one owner.

  • A group cannot be assigned the Is Owner permission as an owner.

  • Jobs triggered through Run Now assume the permissions of the job owner and not the user who issued Run Now.

  • Jobs access control applies to jobs displayed in the Lakeflow Jobs UI and their runs. It doesn't apply to:

    • Notebook workflows that run modular or linked code. These use the permissions of the notebook itself. If the notebook comes from Git, a new copy is created and its files inherit the permissions of the user who triggered the run.

    • Jobs submitted by API. These use the notebook's default permissions unless you explicitly set the access_control_list in the API request.

MLflow experiment ACLs

MLflow experiment ACLs are different for notebook experiments and workspace experiments. Notebook experiments cannot be managed independently of the notebook that created them, so the permissions are similar to notebook permissions.

To learn more about the two types of experiments, see Organize training runs with MLflow experiments.

ACLs for notebook experiments

Changing these permissions also modifies the permissions on the notebook that corresponds to the experiment.

Ability

NO PERMISSIONS

CAN READ

CAN RUN

CAN EDIT

CAN MANAGE

View notebook

Comment on notebook

Attach/detach notebook to compute

Run commands in the notebook

Edit notebook

Modify permissions

ACLs for workspace experiments

Ability

NO PERMISSIONS

CAN READ

CAN EDIT

CAN MANAGE

View experiment

Log runs to the experiment

Edit the experiment

Delete the experiment

Modify permissions

MLflow model ACLs

This table describes how to control access to registered models in workspaces that are not enabled for Unity Catalog. If your workspace is enabled for Unity Catalog, use Unity Catalog privileges instead.

Ability

NO PERMISSIONS

CAN READ

CAN EDIT

CAN MANAGE STAGING VERSIONS

CAN MANAGE PRODUCTION VERSIONS

CAN MANAGE

View model details, versions, stage transition requests, activities, and artifact download URIs

Request a model version stage transition

Add a version to a model

Update model and version description

Add or edit tags

Transition model version between stages

Approve a transition request

Cancel a transition request

Rename model

Modify permissions

Delete model and model versions

Notebook ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN RUN

CAN EDIT

CAN MANAGE

View cells

Comment

Run using %run or notebook workflows

Attach and detach notebooks

Run commands

Edit cells

Modify permissions

note

The workspace UI refers to view-only access as CAN VIEW, while the Permissions API uses CAN READ to represent the same level of access.

Pool ACLs

Ability

NO PERMISSIONS

CAN ATTACH TO

CAN MANAGE

Attach cluster to pool

Delete pool

Edit pool

Modify permissions

Query ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN RUN

CAN EDIT

CAN MANAGE

View own queries

See in query list

View query text

View query result

Refresh query result (or choose different parameters)

Include the query in a dashboard

Change SQL warehouse or data source

Edit query text

Modify permissions

Delete query

Legacy SQL editor query ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN RUN

CAN EDIT

CAN MANAGE

View own queries

See in query list

View query text

View query result

Refresh query result (or choose different parameters)

Include the query in a dashboard

Edit query text

Change SQL warehouse or data source

Modify permissions

Delete query

Secret ACLs

Ability

READ

WRITE

MANAGE

Read the secret scope

List secrets in the scope

Write to the secret scope

Modify permissions

Serving endpoint ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN QUERY

CAN MANAGE

Get endpoint

List endpoint

Query endpoint

Update endpoint config

Delete endpoint

Modify permissions

SQL warehouse ACLs

Ability

NO PERMISSIONS

CAN VIEW

CAN MONITOR

CAN USE

IS OWNER

CAN MANAGE

Start the warehouse

View warehouse details

View warehouse queries

Run queries

View warehouse monitoring tab

Stop the warehouse

Delete the warehouse

Edit the warehouse

Modify permissions

Vector search endpoint ACLs

Ability

NO PERMISSIONS

CAN CREATE

CAN USE

CAN MANAGE

Get endpoint

List endpoints

Create endpoint

Use endpoint (create index)

Delete endpoint

Modify permissions