Departments and outlets let an authorized organization describe operational scope and assign people or recipient destinations where the product supports them. The structure available to you is determined by your role, organization, property, and current configuration. Do not assume every property uses the same levels, routes, QR format, reporting breakdown, or guest-payment behavior.
Confirm your authority and active scope
Before creating or changing structure, confirm the signed-in organization, property, role, and available management capability. A department or outlet name is not authority to access every person, record, payment, or financial detail below it. Ask an authorized administrator to grant or correct scope when a required control is unavailable.
Do not make operating changes while a property data-mode transition is active; payments and operating actions can pause until the transition is verified.
Use currently available structure controls
Use only the Business structure controls visible to your authorized scope to create, edit, or assign a department or outlet. Confirm parent/child and recipient relationships in the saved record after a change. Do not promise a fixed menu path, default preset, guest-facing description, instant propagation, or ability to delete or reorder a structure item from this guide.
When you assign a person, use the authorized team workflow and review the resulting assignment. Role, capability, hierarchy, and environment checks still apply after the assignment is saved.
Treat guest entry points as configuration-dependent
If the product shows a published guest entry point for an authorized recipient, confirm its displayed recipient and active environment before sharing it. A department or outlet record does not by itself create a guest entry point, enable a QR code, permit a payment method, create an allocation rule, or make a Wallet or payout available. Do not infer a result in Live from a related Sandbox or Demo record.
Review outcomes through authorized records
Use the reporting and operational controls currently available to your scope to review recorded activity. Do not promise a particular analytics breakdown, timing, rating, tip, payment, allocation, or payout outcome. For a question or unexpected configuration, share the authorized scope, displayed environment, approximate time, and a non-sensitive reference; never share card data, bank data, passwords, verification codes, or tokens.