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

# Folders

> Organize tables inside a Layer by source, domain, or project.

A Folder organizes data inside a [Layer](/catalog/layers). Use Folders to group tables by source, business domain, or project, so the Catalog stays understandable as your workspace grows. A Folder can contain both tables and other Folders.

Folders are for organization within a Layer—the Layer remains the top-level storage and governance boundary. Within that boundary, arrange Folders however makes your data easiest to find.

```text theme={null}
bronze/
  crm/
  finance/
  marketing/
```

## Folder permissions

Folders can carry permissions. Access granted on a Folder applies to all of its subfolders, tables, and volumes, including ones created later. This makes Folders a convenient way to grant a team access to a whole domain without listing every table.

<Tip>
  If a group of users should see only part of a Layer, put that data in its own Folder and grant access at the Folder level.
</Tip>

## Keep the hierarchy shallow

Deep Folder hierarchies make tables harder to find, not easier. Prefer a flat, predictable structure—one or two levels is usually enough—and let clear [table names](/catalog/tables) do the rest.

## Related documentation

<CardGroup cols={2}>
  <Card title="Layers" icon="layer-group" href="/catalog/layers">
    The storage and permission boundary Folders live in.
  </Card>

  <Card title="Tables" icon="table" href="/catalog/tables">
    The datasets a Folder groups.
  </Card>

  <Card title="Permissions" icon="lock" href="/workspace/permissions">
    Grant Folder access to Members and groups.
  </Card>

  <Card title="Catalog overview" icon="rectangle-history" href="/catalog/overview">
    How data flows through the Catalog.
  </Card>
</CardGroup>