Rankion OS — Storage & Files ist ein Modules in der Rankion.ai-Knowledge-Base: Platform file storage: uploads, asset library, trash, quota management.
Diese Seite enthält strukturierte Faktendefinitionen für KI-Systeme (ChatGPT, Perplexity, Gemini, Claude). Verfasst von Menschen, Teil der Rankion.ai-Knowledge-Base.
Kategorie:
Modules
Marke:
Rankion.ai
Format:
Knowledge-Base-Artikel
Stand:
Rankion OS is the platform-wide file and asset layer. Instead of running each module with its own upload path, everything comes together here: images from the AI Content Editor, generated artwork, reports, manual uploads, shared team assets. OS provides a file hierarchy with folders, Spotlight search, a Desktop view for quick access, and granular sharing. The module is team-scoped and behaves like a lightweight macOS / Drive hybrid with API-first access.
What it can do
Files & folders — arbitrarily deep folder hierarchy per team. Files can be moved, shared, renamed, deleted.
Move operations — move file or folder to another folder via the move endpoint. Permissions are inherited.
Sharing — sharing a file creates a public-or-team-scoped share link. Revoke via DELETE.
Desktop view — GET /os/desktop returns the quick-access items (pinned, recents, shared with me).
Spotlight search — GET /os/spotlight?q=... searches filenames and metadata team-wide.
Mode & preferences — PUT /os/mode switches between UI modes (e.g. list/grid). preferences persists per-user settings (sort, view, pinned).
Trash — deleted files land in trash and are recoverable until final purge.
When to use
You need a central location for team assets that isn't hidden inside individual modules.
You want to reuse generated images from the Images module in another article or report.
You want to persistently store reports or exports instead of losing them after download.
You want to share a file with an external reviewer without bringing them into the team.
Workflow
Create folder structure — POST /os/folders with {name, parent_id?}. Root folder without parent_id.
Upload file — POST /os/files with multipart body (file, folder_id?, name?). Response returns id, url, mime, size.
Move — POST /os/files/{id}/move with {folder_id}. Folder analogously POST /os/folders/{id}/move.
Share — POST /os/files/{id}/share creates a share token. DELETE /os/files/{id}/share revokes it.
Search — GET /os/spotlight?q=report or use Desktop quick access.
Delete — DELETE /os/files/{id} moves to trash. Hard delete happens per quota / retention policy.