Settings
Settings
Tenant-level configuration: defaults, integrations, language preferences, SMTP, and any other tenant-wide knobs.
In this section
- Tenant Configuration (this page) — defaults that apply across the tenant
- Integrations — Hospitable, WhatsApp Cloud API, Nuki, 2N
Tenant Configuration
The Tenant Configuration page (/v28/settings/configuration or the legacy /configuration) collects every tenant-wide default.

Language defaults
tenant_default_target_language— fallback outbound language when no teammate is assigned to a reservation. Typically your operator's language (enfor FlatsBratislava).tenant_no_translate_languages— list of languages to preserve verbatim across the whole tenant. Falls back to teammate-levelnoTranslateLanguageswhen set.
See Communications → Languages for the full decision tree.
Email (SMTP)
Per-tenant SMTP configuration for outbound email (invoices, owner statements). Foundation deployed Q3 — currently functional for invoice sends; the templates editor UI and full integration are tracked in the Email Feature memory and ongoing tickets.
Fields:
- SMTP host, port, username, password (encrypted at rest)
- From-address (used in
From:header) - Reply-to address
- Test-send button
City tax
Per-tenant tax rates and reporting setup. See docs/city-tax-monthly-reporting.md for the rate structure and monthly report format.
Other knobs
- Default check-in / check-out times (fallback when a property doesn't specify)
- Currency (per tenant; reports respect this)
- Tenant slug (read-only after creation — this is what shows in the webhook URL path)
Related issues
- #85 — Operational hygiene:
.env.example, key rotation docs, attachment tenant-scoping. - #137 — NULL
propertyName(relates to defaults applied at property level, not tenant; cross-reference). - #218 —
whatsappPhoneNumberIdtenant config field (see Integrations).
Source: the FlatsBratislava operator manual.