> ## Documentation Index
> Fetch the complete documentation index at: https://docs.k16solutions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lakehouse overview

> Publish, import, snapshot, export, and govern DataX entities in Lakehouse.

Lakehouse is the operational workspace for governed DataX entities. Use it after you have explored or authored data in the Catalog and Worksheets.

<Note>
  Lakehouse areas appear only when they are enabled for your workspace. Management actions can
  require additional role access.
</Note>

<CardGroup cols={2}>
  <Card title="Deployments">
    See which blueprint version is live, compare versions, and manage staged changes. [Manage
    deployments](/datax/lakehouse/deployments).
  </Card>

  <Card title="Imports">
    Upload CSV files, review inferred columns and sample rows, and publish an imported entity.
    [Import CSV data](/datax/lakehouse/import-csv-data).
  </Card>

  <Card title="Snapshots and exports">
    Capture published blueprint data now or on a schedule, and prepare file exports. [Create
    snapshots](/datax/lakehouse/snapshots).
  </Card>

  <Card title="Column constraints">
    Classify sensitive columns so data access rules can mask protected values. [Manage column
    constraints](/datax/lakehouse/column-constraints).
  </Card>
</CardGroup>

## How assets move through Lakehouse

1. You create and validate a blueprint in the Catalog.
2. Publishing creates a version, stages it, and applies it.
3. **Deployments** identifies the live version and any available or staged target.
4. Published blueprints become available to snapshot and export schedules.
5. Column classifications and role access continue to govern returned values.

CSV imports follow a related flow: create the import configuration, upload and scan files, review the inferred schema, then publish the resulting entity to the Catalog.

## Operational checks

Before you deploy or schedule a job:

* confirm the entity is published and enabled;
* review the live and target version;
* check the entity's lineage and downstream consumers;
* verify column classifications and role access;
* confirm that the schedule uses the intended blueprint;
* wait for an in-progress action to finish before starting another one.

<Warning>
  Lakehouse actions can affect downstream queries and create persistent data or files. Review the
  target, version, cadence, and access before you confirm an action.
</Warning>