Skip to content

Tasks support file attachments, uploaded by drag-and-drop from the front end or wp-admin. Attachments are private to the project and are never exposed through a public media URL.

  • Open a task (from any board, list, calendar or notification) and drag files onto the dropzone in the task panel, or click to choose them.
  • Only users with write access to the project can upload; viewers and clients see attachments read-only.
  • Click the × next to a file and confirm. A file uploaded to the task is deleted for good; there is no trash to restore it from.
  • A file attached from the Media Library through the REST API is only taken off the task and stays in the library.
  • Deleting a task deletes the files uploaded to it.
  • Files are stored in a protected directory (kanbanomy-private/) with randomized filenames, not in the normal uploads folder.
  • Each download runs through a permission-checked REST route that verifies the requester can read the project before serving the file. A direct guess at the file path does not work.

This means a private project’s files stay private - the same visibility rules that protect the project’s tasks and milestones protect its attachments. The interface only ever links to the permission-checked route, never to the raw file.

Files are stored under wp-content/uploads/kanbanomy-private/ with random, unguessable names, and Kanbanomy ships an .htaccess that denies direct access on Apache. Nginx does not read .htaccess, so for defense in depth on Nginx add a deny rule for that path, for example:

location ^~ /wp-content/uploads/kanbanomy-private/ { deny all; return 403; }

Without it, attachments remain protected by the permission-checked route and their unguessable filenames (the direct URL is never shown in the UI), but the raw path is not additionally blocked at the web-server layer.

The allowed file types, maximum size, and maximum number of attachments per task are controlled by filters, so a developer can tighten or loosen them per site. See the kanbanomy_attachment_* filters in the Developer guide.