Databricks recommends managing all init scripts as cluster-scoped init scripts. Init scripts should be stored in Unity Catalog volumes if using compute with shared or assigned access mode. Workspace files should be used for init scripts if using compute with no-isolation shared access mode. For more on creating volumes, see Create volumes.
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?.
Init scripts can be stored in any location the user uploading the init script has proper permissions. See Folder permissions.
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 permissions.
Some ACLs are inherited from directories to all files within a directory.
Init scripts in workspace files are intended for use as cluster-scoped init scripts. See Use cluster-scoped init scripts.