Authorization, acquisition
and delivery evidence.

Give each person and integration the right access

Named accounts, groups, roles, mailbox permissions and scoped API keys control access. The server checks console and integration requests. Assigning a document to someone does not grant them access to its mailbox.

Audit records help you review configuration and access changes. Each accepted send keeps its attempt and provider binding, so a later account change does not silently move an in-flight document to different credentials.

Know what happened to the document

A received-fax notification waits for its actual document to be acquired and checked. An uncertain send waits for reconciliation instead of being blindly transmitted again. Document acquisition, transport delivery, email delivery, owner acknowledgement and completion remain separate events.

Verified direct partners exchange encrypted originals and signed receipts. Recipient approval governs document reuse. Ordinary carrier fax follows the capabilities of its carrier and media path; it does not inherit the protection of the direct-delivery channel.

Define the deployment boundary

Faxbot supports a dedicated installation for each organization. Set the HTTPS endpoints, provider callback checks, network exposure, storage protection, cleanup settings and backups for that installation. Mailbox permissions organize access within it; they do not create separate tenants.

Review each provider and email destination that handles documents. Encryption at rest, backup protection and operational recovery depend on the storage and deployment you configure.

In the current release

Carry policy through the delivery

Versioned routing rules constrain accounts, delivery channels, cost caps and approval holds at organization, mailbox and workflow scope. The accepted job records those decisions, and later attempts stay inside its permitted routes.

Broader enterprise controls—including legal holds across managed copies, exact-action approvals, workforce provisioning and source-backed industry templates—remain planned work. Configure only the controls present in your installed version.

Fit the controls to your obligations

For healthcare or other regulated work, define the service scope, provider agreements, processing rules and operating procedures your organization needs. Technical features alone do not establish compliance or certification.

The public console is a restricted, read-only view of a real installation. It does not accept fax documents or validate a regulated workflow.