Originally created by @le-patenteux on GitHub (Jun 26, 2025).
Originally assigned to: @tjbck on GitHub.
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
We are using the Knowledgebase a lot, and have created dozens of knowlege bases. Same goes for custom Models. Our issue is that it becomes harder and harder to navigate.
A simple folder structure would do a lot to help on that front.
Desired Solution you'd like
Simply adding a grouping functon, akin to a folder structure...
Not sure I need to make a detailed post suggesting how a folder hierarchy works, but I will do it if needed ☺️
Alternatives Considered
I don't really see better ways... maybe I am not really imaginative when it comes to organizing...
Additional Context
the cluttered mess we created!
Originally created by @le-patenteux on GitHub (Jun 26, 2025).
Originally assigned to: @tjbck on GitHub.
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
We are using the Knowledgebase a lot, and have created dozens of knowlege bases. Same goes for custom Models. Our issue is that it becomes harder and harder to navigate.
A simple folder structure would do a lot to help on that front.
### Desired Solution you'd like
Simply adding a grouping functon, akin to a folder structure...
Not sure I need to make a detailed post suggesting how a folder hierarchy works, but I will do it if needed ☺️
### Alternatives Considered
I don't really see better ways... maybe I am not really imaginative when it comes to organizing...
### Additional Context
the cluttered mess we created!

@tjbck I would argue hierarchies are still very practical to have a single overview of what's there. So maybe allow top-level tags to be listed as hierarchies?
@ion-elgreco commented on GitHub (Jun 30, 2025):
@tjbck I would argue hierarchies are still very practical to have a single overview of what's there. So maybe allow top-level tags to be listed as hierarchies?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @le-patenteux on GitHub (Jun 26, 2025).
Originally assigned to: @tjbck on GitHub.
Check Existing Issues
Problem Description
We are using the Knowledgebase a lot, and have created dozens of knowlege bases. Same goes for custom Models. Our issue is that it becomes harder and harder to navigate.
A simple folder structure would do a lot to help on that front.
Desired Solution you'd like
Simply adding a grouping functon, akin to a folder structure...
Not sure I need to make a detailed post suggesting how a folder hierarchy works, but I will do it if needed ☺️
Alternatives Considered
I don't really see better ways... maybe I am not really imaginative when it comes to organizing...
Additional Context
the cluttered mess we created!
@tjbck commented on GitHub (Jun 27, 2025):
You can utilise tags for this purpose, will add a tag filter view to model workspace!
@ion-elgreco commented on GitHub (Jun 30, 2025):
@tjbck I would argue hierarchies are still very practical to have a single overview of what's there. So maybe allow top-level tags to be listed as hierarchies?