Skip to main content
A Folder organizes data inside a Layer. 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.

​
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.
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.

​
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 do the rest.

​
API & MCP

Platform API

Read the Folder object.

MCP tools

No dedicated folder tool yet.

Layers

The storage and permission boundary Folders live in.

Tables

The datasets a Folder groups.

Permissions

Grant Folder access to Members and groups.

Catalog overview

How data flows through the Catalog.