Customization

📄️ Init Scripts & Dependencies

There are three places to put setup that runs before your notebook does anything: a global script that the platform runs everywhere, a runtime script attached to a specific runtime template, and a per-notebook script that you write yourself. Each layer can build on, or override, the one before it. This article explains the three layers, how they execute, where to write each one, and how to declare Python and JAR dependencies that the platform installs for you.

📄️ Notebook Utilities (synutils)

Every Syntasa notebook ships with a unified utility namespace called synutils. It is the one entry point for everything the platform exposes to your code: secrets, package installs, notifications, connection metadata, the data registry, Spark helpers, cloud storage, and uploaded files. Using synutils instead of pulling in raw SDKs means you get the platform's auth, credential decryption, and integration plumbing for free, in one consistent shape across Python and Scala.