We are trying to replace our team’s Boards App with the Library, however we can only do parent level folder structure. This is causing some organizational chaos because in Boards, we have folders like “Product Info” or “Installation Resources” for our products and within those folders are broken down into different models, types of installs, etc. To convert this into the Library, we would either need to have one parent-level folder that just has all the install docs, videos, and resources for all models in one folder (which means the folders get overwhelmingly full of resources) or we have a bunch of folders like Product info - A and Product Info - B (which results in an overwhelming looking root-level of the library with so many folders, but then each folder has just the few resources relevant to that folder). While I understand that the library is searchable, which is great and alleviates part of this stress, having nested folders would be exceptionally helpful for the visual folks who operate in folders to find resources or don’t recall the name of the file / resource they’re looking for.
Completed
Feature Request
10 months ago

McKenna
Get notified by email when there are changes.
Completed
Feature Request
10 months ago

McKenna
Get notified by email when there are changes.