Tenant settings

Branding, localisation, security policies, and module toggles at tenant level.

1 min readLast updated 13 Apr 2026

Tenant settings control cross-module behaviour. Lives at /app/admin/tenant-settings — TENANT_ADMIN role.

Sections

Branding

Logo, colours, fonts, footer text, bank details. Applies to documents, emails, portal. See branding.

Localisation

  • Home currency.
  • Base language.
  • Date / number formats.
  • Timezone.
  • Business calendar (holidays, working days).

Security

  • Password policy.
  • MFA requirement.
  • SSO configuration (SAML / OIDC).
  • Session timeout.
  • IP allowlist.

See security.

Modules

Toggle which modules are active for the tenant:

  • Forwarding (air, sea, road).
  • Warehousing.
  • Customs.
  • CRM.
  • Finance (AR, AP, taxes).
  • Mobile (driver, warehouse).
  • Customer portal.

Turning a module off hides menus but preserves data.

Document numbering

Per-doc-type numbering sequences: prefix, padding, starting number, reset cadence (yearly / never). Example: QT-2026-000123.

Email / notifications

  • Outbound email provider (SES, SendGrid, SMTP relay).
  • Default from / reply-to.
  • Per-event notification toggles.
  • Digest cadence for non-urgent events.

FX + tax

  • FX provider.
  • Tax codes.
  • VAT / GST registration numbers per country.
  • E-invoicing credentials where required.

Integrations

Jump-point to integrations.

Data retention

Per-record-type retention overrides. Defaults cover most needs.

Change control

Settings changes are audited. High-impact changes (security, modules, branding, numbering) trigger a confirmation dialog and write a verbose audit entry.

Multi-entity

Multi-entity tenants have a shared-settings layer + per-entity overrides.

Was this article helpful?