Build a folders-first structure
Managers can create a hierarchy up to the supported depth, then place files and links in the appropriate folder. Mobile removes redundant headings while desktop keeps the wider Library context and controls.
Organize community knowledge into folders, files, links, media, previews, search, and explicit viewer or editor access.
Files and links shared only in a feed become difficult to recover and easy to misunderstand. Library gives community knowledge a folder, title, content type, preview, path, and access model. It stays separate from a personal drive: the structure belongs to the community and remains governed by community membership and folder permissions.
Managers can create a hierarchy up to the supported depth, then place files and links in the appropriate folder. Mobile removes redundant headings while desktop keeps the wider Library context and controls.
Add multiple uploaded files or save a URL with fetched title, site, description, and image context. YouTube and Vimeo links are classified as videos and remain eligible for the Videos filter.
Images, PDF, video, audio, and supported document formats use permission-checked in-app viewers. Unsupported legacy binary formats keep a download fallback inside the same viewer rather than silently opening an external service.
A non-empty search can return folders and media or file matches across accessible descendants, including the containing folder path. Selecting a result opens the correct folder, scrolls to the exact item, and briefly highlights it.
Restricted folders can name explicit viewers and editors. Descendants inherit by default and may narrow access, but they cannot broaden the parent’s permissions. Editors manage contents without gaining folder-structure or sharing control.
Open the root or a permitted nested folder and see folders before files and media.
Use content type, scope, or nested search without bypassing access.
Open a saved link, visual tile, or private uploaded file in its appropriate viewer.
Create folders, add files or links, edit metadata, move content, or adjust explicit access.
Admins and moderators manage the folder hierarchy, access settings, moves, and recursive deletion.
Folder editors manage files and links inside their assigned area but cannot change the structure or sharing model.
Uploaded files are delivered through permission-checked endpoints or short-lived authorised URLs rather than public permanent object URLs.
The current plan copy describes limited resources on Sapeans, higher resource storage on Sapeans, and custom resources on Enterprise. The current product label is Library; `/app/resources` remains only a compatibility redirect.
The current Library supports folders, uploaded files, and saved links, with content-aware presentation for images, videos, PDFs, documents, audio, and other supported formats.
Yes. A non-empty search spans accessible nested folders and returns the containing path without bypassing folder permissions.
Admins and moderators manage structure and access. Editors can manage content inside an assigned folder but cannot change its sharing rules.
No. Library files are intended to use permission-checked delivery or short-lived authorised URLs.