Configure data zones, top-level organizational boundaries for storage paths.
## Overview The Zones page is the starting point for establishing the top-level organizational structure of the data platform. Each zone represents a logical boundary that maps to a physical storage path (local filesystem, Azure Blob Storage, or Azure Data Lake Storage) and contains one or more schemas. Platform administrators use this page to define zones that mirror the data architecture tiers (landing, staging, curated, presentation) and to associate zones with workspaces for access scoping. Zones are the coarsest unit of organization in the catalog hierarchy. All schemas, tables, and views ultimately reside within a zone, making zone configuration a prerequisite for any downstream catalog operations. ## Key Features - **Zone creation and management.** Create new zones, edit zone properties, and remove empty zones. Each zone requires a unique name and a description that clarifies its purpose within the data architecture. - **Storage path configuration.** Assign a root storage path to each zone. The path determines where Delta Lake tables within the zone persist their data files. Supported path schemes include local filesystem paths and cloud storage URIs. - **Workspace association.** Link zones to one or more workspaces so that workspace users can browse and query only the zones relevant to their work. This association enforces logical access boundaries without requiring row-level security. - **File upload to zone storage.** Upload CSV, Parquet, JSON, and other supported file formats directly into a zone's storage path from the browser. Uploaded files become available for ingestion into Delta Lake tables via pipelines or ad-hoc SQL commands. ## Workflow 1. Open the Zones page from the Configuration sidebar. 2. Click the add zone button and provide a unique zone name and description. 3. Configure the root storage path for the zone (local path or cloud storage URI). 4. Associate the zone with one or more workspaces. 5. Optionally upload seed data files into the zone storage path. 6. Proceed to the Schemas page to create schemas within the newly configured zone. 7. Review zone settings periodically as storage requirements and workspace assignments evolve.