Support folders/grouping for Workflows, Chatflows, and Knowledge to organize apps

The request concerns the Studio and Knowledge list pages, including their folder, breadcrumb, move, search, and filter behavior. Start by tracing how those pages currently load and organize apps and knowledge bases, then identify the existing persistence and API paths for tags or similar metadata. Done means folders can be managed and items moved without changing runtime or API behavior, while root items and existing search remain supported.

Self Checks

• I have read the Contributing Guide and Language Policy.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

As I build more Workflows, Chatflows, and Knowledge bases in Dify, the list pages (Studio and Knowledge) become very long and flat. Everything is shown in one place, so it takes a lot of scrolling and searching to find the app or dataset I need. It is even harder when I work on several projects or clients at once, because apps from different projects are mixed together.

Right now the only ways to cope are tags, search, and naming conventions (e.g. prefixing names with "ProjectA - ..."). These help, but they don't give a real structure, and the list still gets cluttered as it grows. It is frustrating to manage dozens of items this way, and it's easy to accidentally edit or delete the wrong one.

I would like a folder-based grouping feature, similar to folders in Google Drive or Notion, so items can be organized hierarchically and only the relevant ones are shown at a time.

Proposed behavior:

• Create, rename, and delete folders in Studio (for Workflow, Chatflow, and other app types) and in the Knowledge page.
• Move apps/knowledge bases into a folder (via drag and drop or a "Move to folder" action).
• Show only the items of the current folder, with breadcrumb navigation to go back to the parent.
• (Optional) Support nested sub-folders.
• Items not in any folder stay at the root level, so existing setups are not affected.
• Search and filters should still work, ideally searching across all folders or within the current folder.
• Folder assignment should be organizational only, so it should not change how apps or knowledge bases run, or affect their API access.

2. Additional context or comments

• Existing tags are useful for cross-cutting labels, but they don't reduce the clutter of the main list. Folders and tags could complement each other.
• Related use case: teams or workspaces with many apps would benefit from this, especially when separating projects, environments (dev/staging/prod), or clients.
• Reference UX: folder handling in Google Drive, Notion, or n8n's projects/folders.

3. Can you help us with this feature?

• I am interested in contributing to this feature.