Folder Organization

Let people group files into nested folders instead of one endless list.

moderate Documents & Files

What it adds

A folder tree over the app's existing files, with move, rename, breadcrumbs, and per-folder listing.

What your agent is told to do

1
Add a parent reference to the app's existing file records rather than creating a second storage model. Files already uploaded belong at the root, not in a migration limbo.
2
Build the listing on top of the existing file list and Attachment Gallery views. Extend those with a breadcrumb and a folder row type rather than shipping a second file browser beside them.
3
Support moving files and folders by both drag and an explicit move dialog, because drag alone is unusable on touch and with a keyboard.
4
Enforce folder permissions on the server for every read, move, and delete. A user who cannot see a folder must not be able to move a file into it or guess its contents from an error message.
5
Do not build a general-purpose filesystem with symlinks, shortcuts, or a file living in two folders at once. One parent per item covers the real need and keeps counts, deletion, and permissions comprehensible.

Edge cases it handles

Moving a folder into one of its own descendants would detach the whole subtree from the root and make it unreachable. Walk the ancestor chain before accepting a move and refuse with a clear message.
Deleting a folder that still has contents needs a decided, documented answer: refuse while non-empty, cascade to the trash, or promote the children to the parent. Pick one, say so in the confirmation, and never leave orphaned files pointing at a folder that no longer exists.
Unlimited nesting produces breadcrumbs that wrap over three lines and paths too long for the archive and export paths. Cap the depth, enforce the cap on move as well as on create, and say what the limit is when it is hit.
Item counts and folder sizes computed at write time drift after a bulk move or a partially failed one. Either derive them on read or recalculate them in the same transaction as the move.
Two people renaming the same folder at once must not produce a lost update or two siblings with the same name. Resolve on the server, and tell the loser what the folder is now called instead of silently reverting their input.
Names that differ only by case, trailing spaces, or invisible characters read as duplicates to a human. Normalise before the uniqueness check within a parent.
A file whose folder was deleted or moved while the user had the listing open must not vanish without explanation. Refresh the view and say what changed.
Search must span folders rather than only the folder currently open, and each result must show the path it lives at.

Definition of done

Files and folders can be created, renamed, moved, and deleted, and the tree survives a reload.
A folder cannot be moved inside itself or any of its descendants.
Deleting a non-empty folder follows one documented behaviour, stated in the confirmation.
Nesting depth is capped and the cap is enforced on move as well as create.
Item counts and sizes stay correct after a bulk move.
Folder permissions are enforced server-side on read, move, and delete.
Search returns matches from every folder the user can see, each showing its path.
The feature matches the existing design system.
No existing functionality is broken.

Related features

PDF Converter

Fillable PDF Forms

Document Scanner

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.