Property settings can expose configuration controls for the selected Business scope when your role, capabilities, and assignments permit them. The current product—not this guide—determines which settings, values, approval steps, environments, records, and save actions are available. Do not assume every property has the same tabs, defaults, thresholds, room data, automation, commission, finance, document, maintenance, or environment control.

Confirm scope and environment before a change

Confirm the selected organization or property, the active environment, the visible setting, and the current value before changing a configuration. Live, Sandbox, and Demo records are separate. A setting, test, transaction, guest flow, report, payment, allocation, Wallet balance, or payout result outside Live does not prove the corresponding Live behavior.

Use only the confirmation and authorization flow shown by the product. A visible field or page does not override server-enforced permissions, scoped assignments, validation, current policy, provider state, or an organization’s operating process.

Avoid unsupported operational and financial promises

Do not use a property setting to promise a rating threshold, automatic recovery action, guest contact, room association, commission split, recipient amount, financial ledger, payroll instruction, tax treatment, payment method, refund, reversal, payout eligibility, bank deposit, notification, data retention, or timing. Those outcomes require the applicable current product, provider, policy, and authorized workflow.

If a change affects staff or guests, use approved internal review and communication procedures. Do not publish personal, payment, bank, identity, guest, room, or employee data in a setting, document, link, or support request.

Report a configuration issue safely

For an issue, provide the authorized property scope, active environment, setting label, displayed current value, approximate time, and non-sensitive error or reference. Support can investigate the recorded state but cannot bypass organization authorization or safely infer an intended financial or operational outcome.