Store init scripts in workspace files

Databricks recommends managing most init scripts as cluster-scoped init scripts stored in workspace files. If you are using Databricks Runtime 13.3 LTS and above with Unity Catalog, Databricks recommends using Unity Catalog volumes for init scripts.


While init scripts stored in workspace files generally act like other workspace files, Databricks has configured support for init scripts in all currently supported Databricks Runtime versions.

For more on workspace files, see What are workspace files?.

Where are init scripts stored in workspace files?

Init scripts can be stored in any location the user uploading the init script has proper permissions. See Folder ACLs.

Like all workspace files, init scripts use access control lists (ACLs) to control permissions. By default, only the user uploading an init script and workspace admins have permissions on these files. See File ACLs.


Some ACLs are inherited from directories to all files within a directory.

Use init scripts stored in workspace files

Init scripts in workspace files are intended for use as cluster-scoped init scripts. See Use cluster-scoped init scripts.