Project files

Files is a project-level lens over every attachment already living on that project’s tasks and comments. It exists for one question: where did that screenshot go? — answered without remembering which task it was on.

What you see

Each row shows the filename, whether it is an image or a document, its size, who uploaded it, when, the task it belongs to, and whether it was attached on the task or in a comment. Click the filename to download; click the task identifier to open that task — the Files view stays behind the pane, and refreshing keeps the split.

Switch between a dense list and a thumbnail grid with the layout buttons. Both are fully keyboard accessible; the layout is a personal preference and is not shared.

Filters

Four facets, each backed by real stored data:

• File type — images or documents, decided by the stored content type rather than the filename, so a mislabelled .png is classified honestly.
• Uploader — anyone in the workspace.
• Source task — any task in the project.
• Uploaded — any time, or the last 7 / 30 / 90 days.

Filters live in the URL, so a narrowed view is shareable and survives a refresh.

What Files does not do

You cannot upload here. Files are attached on a task or in a comment, where they have a subject; the project lens finds them again afterwards. This is deliberate, not a gap waiting to be filled.

Everything downloads through ScopeKite’s own guarded route with the same permission check as the task it belongs to. Storage locations are never exposed to the browser, and SVG files are never rendered inline — they download like any other document, because an SVG can carry script.

Deleting an attachment on its task removes it from this view too.