Protecting freight records through the workflow.
Last updated September 26, 2026. This page describes current product practices. Hosting, identity, storage, and operational configuration also affect how those practices work in each deployment.
Organization access
Workspace records are scoped to an organization. Users must authenticate, and role permissions control access to review and administrative actions. CargoMends checks organization ownership when workspace records and files are read or changed.
Private documents
Uploaded freight documents are intended to remain private to the organization that provided them. File access goes through authorized application routes or short-lived signed access where the configured storage provider supports it. Source documents remain linked to their extraction and review provenance.
Integration credentials
Integration credentials are encrypted before storage and are not returned through ordinary client APIs or included in organization exports. Connected providers may have separate permission, consent, and security settings that administrators should review before enabling an integration.
Workflow history and human approval
Important workflow actions, including review decisions, dispute transitions, and data-control requests, are recorded in activity history. Findings remain subject to human review; the product does not autonomously approve payments or send disputes without an explicit human action.
Configuration and questions
Security controls depend on the deployment and enabled providers. Some operational controls and retention tasks require administrator configuration. For a security or privacy question, contact support@cargomend.com. Do not include passwords, credentials, or private invoice attachments in an initial message.