Shadcn Tree Permissions

When to use

• Folder and file explorers for a code project, a workspace or a document store
• Record hierarchies such as CRM accounts and contacts, or an org chart of who reports to whom
• Role permission editors grouped by area, where each action is ticked on or off

When not to use

• Area rows that tick or clear every action under them and show a mixed state: use the Cascader component
• A whole drive page with a folder rail beside a listing of the open folder: use the Files blocks
• Folder rows with size and item count columns that move into other folders by pointer: use the Drag & Drop blocks

Agent notes

• Grants live in local checked state seeded with 5 ids; save them to your API from togglePermission
• Only leaf rows render a Checkbox, so an area row cannot grant or clear its whole group
• syncDataLoaderFeature throws when getItem returns nothing or a promise, so children fetched from a server need the async data loader feature
• The rootItemId record is never drawn, so its children form the top level and its own name stays hidden
• After adding, moving or removing records behind dataLoader, call rebuildTree on tree, or the rows keep the old structure

Third-party API docs

• Headless Tree v1: API reference, docs