SupportMesh

Documentation

Setup, support workflows, delivery operations, and developer integration references for the features SupportMesh currently ships.

/ or Ctrl+K

SupportMesh Docs

Attachments

Keep support files private, track where each file belongs, and understand the explicit security states exposed by the current upload flow.

Where attachments belong

  • Ticket-level attachments
  • Public reply attachments
  • Internal-note attachments

Attachment uploads are prepared and finalized through authenticated routes. SupportMesh stores files privately and serves downloads through authorized signed links.

Attachment states

StateWhat it means
PendingThe file exists in the workflow but has not reached an approved state.
ApprovedThe file is cleared for normal use.
BlockedThe file failed a policy check and should not be treated as available.
FailedThe upload or follow-up processing could not complete.

No unsupported scanning claim

The current worker foundation explicitly keeps finalized attachments in a pending state until a trusted scanner is introduced. Treat file approval as pending unless your own operational controls say otherwise.

Privacy and download behavior

Downloads are authorized per user and generated through short-lived signed links. Internal-note attachments stay within internal access boundaries and should not be treated as client-visible files.