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

# Working with lakehouse data

> Browse shared namespaces, query tables, and review table documentation and lineage

You use lakehouse data in Athena to explore tables that syncs copy from connected sources or transform projects publish. A namespace groups tables and controls your access to them. Open a shared namespace when you need to inspect its data, run a read-only query, or understand where a table comes from before using it in analysis.

## Inspect a table

1. Open the lakehouse namespace shared with you. Find it with **Search Assets**, or open the link it was shared with.
2. Select **Browser** to browse its tables, or **Schema** to inspect column definitions.
3. Choose a table under **Tables** on the **Overview** to open its own page. Review **Schema**, **Sample**, and **Snapshots** (shown when the table has snapshots). The table page also shows **Rows**, **Data files**, and **Columns**.
4. Read the table description and check its **Owner**, **Certified**, and **Deprecated** details when present. Use this context to decide whether the table fits your task.

The sample shows up to 20 rows from the current snapshot. It helps you inspect values; it is not the complete table. If your deployment turns off SQL, the card reads **Sample unavailable**.

<Frame caption="How to open a shared namespace and inspect a table's documentation, schema and sample">
  <iframe src="https://player.vimeo.com/video/1234516235?h=1b1c1c6a59&title=0&byline=0&portrait=0&dnt=1" className="w-full aspect-video rounded-xl" frameBorder="0" allow="autoplay; fullscreen; picture-in-picture" allowFullScreen title="How-to: Open a shared namespace and inspect a table's documentation, schema and sample" />
</Frame>

<Accordion title="Steps in this video">
  1. Search for the namespace
  2. Open it
  3. Open a table
  4. Read its documentation
  5. Check the schema
  6. Look at the sample
</Accordion>

## Query your data

1. Open **SQL Editor** from the namespace.
2. Write a read-only SQL query using the table names shown in the namespace. Use filters or aggregates to focus on the data you need.
3. Select **Run** and review the result.

You can also select **Query** on a table when that action is available. It opens a SELECT query in the namespace's editor.

## Follow dependencies

1. Select **Lineage** on the namespace, or find **Lineage** on a table page.
2. Follow the connections to see what feeds the tables and what reads them.
3. Open linked assets that you have permission to view. A table with no recorded lineage shows an empty state.

## Document a table

You need edit access to the namespace for this task.

1. Open the table and select **Document**.
2. Fill in **Description** and **Owner**. Describe what one row represents and who answers questions about the data.
3. Set **Certified** or **Deprecated** as appropriate.
4. Select **Save**. The documentation is stored on the table for other readers to use.

## Good to know

* Lakehouse support must be configured on your deployment. Viewing metadata and lineage requires access to the relevant asset.
* Lakehouse SQL is read-only. You publish data through syncs or transform projects.
* **Certified** and **Deprecated** are documentation flags. Changing them does not delete table data.
* **Description** accepts up to 4,000 characters. **Owner** accepts up to 320 characters.

## Related links

* [SQL queries](./query)
* [Spaces and assets](../concepts/spaces-and-assets)
* [Asset organization](../contextual-knowledge/asset-organization)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.