Skip to main content
Voyant’s travel domains are parts of one managed product. Bookings owns the Booking lifecycle; Finance owns invoices and settlement; Proposals owns sales proposals. The product composes their behavior and preserves each owner’s validation and audit history. Customers do not choose runtime packages or supply route descriptors.

Configure your organization

Use the Operator’s Settings to manage supported extensions and integrations. Access depends on your role and the capabilities available to your organization. Installation configuration belongs to your organization’s regional product data; it does not create a separate runtime or grant deployment authority. Use custom fields for additional information on supported records. Use published HTTP and webhook contracts for external systems. A supported integration may provide credentials, mappings or configuration without becoming an owner of the product’s business tables.

Preserve business commands

Changes to Bookings, invoices, proposals and contracts go through their owned product commands. Approval, permissions, idempotency and transaction rules apply to integrations as they do to the Operator interface. An integration must not replace those commands with direct database writes.

Internal composition

Source descriptors called modules, providers or extensions are internal product implementation details. Voyant owns their composition and deployment. Customer customization uses the integration contracts described above. Historical package releases retain their original terms. See Extend your workflow for choosing the appropriate integration approach.