← Sign in or Sign Up

STAFF SOFTWARE

Terms & Conditions

Updated 8 October 2026 · Version 20261008.1

These terms explain how authorised staff, HODs, GM, MD and authorised accountants use the Lumeirrah Suites software. They cover the Staff Workspace, Stock and Purchase, Bookings, Accounts, Tasks and Memberships. Software access is for hotel work and depends on the permissions assigned to your profile. Read the privacy notice below before accepting.

1 Who may use the software

Use only your own authorised account. A job title does not automatically give access to every software, department or action. MD assigns software access and permissions; authorised managers may manage staff only within the access delegated to them.

Staff normally work with their own assignments and permitted hotel records. HODs normally manage their own department; GM and MD may have wider access. The permissions shown in the software determine what you may actually do. Do not use another person's account to bypass a restriction.

Customer membership registration is a separate service. These staff terms do not replace the customer membership conditions, hotel booking terms, employment contract or applicable law.

2 Your account and security

Sign Up is available only for a staff number authorised in the hotel staff list. Verify the number using the WhatsApp code and then create your password. Password reset also requires verification of your registered number. Keep your password, OTP and management PIN private. Never request an OTP from a customer except as required by the authorised redemption process.

A successful sign-in may remain active for up to 24 hours on that device. Sign out when using a shared phone or computer. A removed account, changed password or changed access can end a session earlier. Do not leave a signed-in device unattended.

Tell hotel management promptly if your phone number changes, a device is lost, you suspect unauthorised access, or a software record looks incorrect. Do not enter API credentials, passwords, bank details or OTPs into chat, task notes or announcements.

3 Staff privacy notice including Anonymous Chat

The Staff Workspace uses your name, registered phone number, department, designation, role, account status and verification information to identify you and control access. Passwords and OTPs are checked using protected hashes. Where imported or entered, joining details, salary and bank information are private staff profile data and are restricted to MD in the staff portal.

Work records can include bookings, guests and their contact numbers, payments, purchase bills, inventory transactions, task evidence, notices, voice recordings, chat messages, timestamps and account activity. These records support hotel operations, approvals, reconciliation, access management and investigation of errors or misuse. Security records may include IP addresses and sign-in activity.

Anonymous Chat hides author names from the normal shared chat view. Other staff, HODs and GM see messages labelled Anonymous. It is not anonymous to the hotel: the system retains an encrypted record of the author's staff identity, department and posting time. A signed-in MD can use protected, PIN-gated access to view who wrote a message. This includes the author's name and staff profile identity. MD author-access events are logged. Do not post if you do not want MD to be able to identify you.

Do not put guest, colleague or vendor personal information in shared chat. Do not publish another person's salary, contact number, medical information, account details or private allegation. Hotel managers must use staff and guest information only for authorised hotel purposes, not personal curiosity or retaliation. A concern may also be raised directly with hotel management instead of using chat.

Hosting and approved service providers process information needed to run the systems. Where enabled, Weazy supplies operational billing or reservation data, and Xobo/WhatsApp handles verification and transactional notifications. These services have their own policies. Separate optional marketing consent is not obtained through this staff-software checkbox.

4 Staff Workspace and hotel instructions

Read hotel instructions and SOPs made available to your profile. An acknowledgement records that you have read the displayed version; do not acknowledge a document you have not read. Ask your HOD or management if an instruction is unclear or conflicts with a safety requirement.

Authorised HODs, GM and MD may publish important text or voice notices. Publish accurate, work-related instructions within your authority. Do not record or upload someone else's private conversation. Notice authors must have permission to use any recording they upload.

Published notices and shared chat are not substitutes for emergency communication. Contact the responsible manager or emergency service directly for urgent safety matters.

5 Stock and Purchase

Enter the correct product, quantity, unit, department, outlet, date, vendor and bill reference. Check case-to-bottle counts and other unit conversions before submitting. Requisitions, purchase orders, purchase inwards, issues, returns and adjustments are different records and must not be used interchangeably.

Issue only stock actually available in the authorised source store or department. A kitchen transfer to a subdepartment is an internal movement, not a new purchase. Do not change a unit label to conceal a quantity discrepancy. Corrections, merges, deletions and opening balances require the relevant permission and must preserve the audit trail.

Follow the GM and MD approval sequence configured for purchase orders. Do not split a purchase to avoid approval. Approved purchase orders may be cancelled only by an authorised person with the required reason; cancellation is not proof that goods were returned or a payment was refunded.

Attach the genuine vendor invoice or scan where required. Verify GST, item discounts, totals and round-off against the bill. A scan or imported row is not automatically proof that a transaction is correct. Report a difference instead of forcing reports to match by creating fictitious entries.

6 Bookings

Record the correct guest name, phone number, outlet, date, room or venue, pax, meal plan, agreed rate, discount reference, payment mode, advance and booking taker's name. A recorded payment must correspond to money actually received; selecting a payment mode alone does not confirm a payment.

Confirmed bookings, partially confirmed bookings and queries are different statuses. A tentative record or query does not reserve inventory unless the software explicitly confirms a reservation. Check availability, venue restrictions and external booking confirmation before assuring a guest that a room or space is booked.

Use only authorised discounts and record the required reason or reference. Do not impersonate a reference provider. Modify or delete a booking only where your permission and the booking status allow it. Check for clashes and record required venue-manager permission before proceeding.

Booking history may be visible to authorised staff using that outlet. Use guest phone numbers only for the relevant hotel service. Do not export or contact guests for personal or unrelated purposes.

7 Accounts

Record sales, expenses, vendor payments, salaries and advances accurately, with the correct date, outlet, category, tax treatment, bill reference and supporting evidence. Gross revenue, discounts, complimentary value, tax, payable amounts, collected amounts and pending balances must remain distinguishable.

Booking advances received for a future service are tracked separately until the relevant event or stay date. A vendor payment settles a payable and must not duplicate the original purchase expense. A staff advance must not be counted again as salary expense without the appropriate settlement.

Review an imported Weazy bill and its outlet mapping before posting. Do not import the same bill twice. API fetch success does not prove that the connected store or the accounting classification is correct. Retain an original provider bill where available; a software-generated view is not automatically the provider's original document.

Bulk approval means you have reviewed every selected purchase bill. An MD-approved payment request is authority to proceed within its terms, not evidence that payment has already occurred. Do not self-approve, invent a receipt or mark a payment paid without evidence. Follow the configured permissions for categories, vendors, reports and financial settings.

8 Tasks and evidence

A draft task is not an assigned task. Set clear requirements, the correct assignee, department and due date when assigning work. Update progress honestly and attach only evidence relevant to that task.

Staff may act only on tasks available to them. HODs review their authorised department; GM or MD may review wider work where permitted. Completing a task is not the same as approval of its proof. Do not approve your own work unless the hotel's authorised workflow permits it.

Do not stage misleading photographs, alter evidence or upload private information unrelated to the task. Ask the responsible manager to correct a mistaken assignment or record.

9 Memberships and voucher redemption

Check the exact voucher book number and registered customer identity before redemption. Redeem only the correct coupon and quantity that the guest is using. Observe the coupon's validity, eligible outlet, minimum spend, exclusions and remaining balance. Software availability does not override the printed or approved customer offer conditions.

Use the guest verification code where the redemption workflow requires it. Do not redeem for a guest without the required verification. Record the actual savings and bill reference where requested; do not invent savings to increase the customer's displayed total.

The redemption-only staff account does not authorise editing customer profiles, granting offers, importing books or changing administration settings. A membership already paid for must not be charged again merely to register it. DOB and optional anniversary information must be used only for the approved membership service.

10 Reports imports and exports

Check report dates, cut-off time, source store, departments, filters, units and tax basis before comparing totals. Main-store reports and all-department reports can differ legitimately. Review any unpriced, unmatched or invalid rows rather than treating an incomplete report as final.

Use the official import template and preview the file where available. Do not upload salary or customer information to the wrong module. Do not overwrite existing records or delete test data from a live system without specific authority and a recovery plan.

Download reports only for hotel work. Keep exported Excel files, PDFs, scans and screenshots secure. Do not send them to personal or outside recipients without appropriate authorisation. Access to a report is not permission to publish its contents.

11 Corrections approvals and records

Check an entry before submitting it. Use the authorised correction, cancellation, merge or archive action and record a truthful reason where required. Do not backdate a change to hide a mistake or delete evidence needed for reconciliation.

Hotel management may review work records and authorised audit logs to investigate errors, protect accounts and manage operations. An audit log is a record of system activity, not automatic proof of wrongdoing. Any personnel action should follow the hotel's approved process and applicable law. These terms do not waive staff rights or authorise unlawful deductions or penalties.

12 Retention and privacy requests

Hotel records and backups are retained for operational, reconciliation, security and applicable legal needs. Access is restricted according to role. Removing a staff account or archiving an entry does not necessarily erase linked invoices, bookings, redemptions, evidence or audit history.

Contact hotel management to request correction of inaccurate staff information, ask about stored data, request a review of access, raise a privacy complaint or ask to withdraw optional data use. Management must review requests against applicable legal and recordkeeping obligations. You may stop using the optional chat; withdrawal does not automatically erase records lawfully retained for a necessary purpose.

The hotel must maintain an approved retention schedule and a designated contact for these requests. No unlimited retention period or guaranteed deletion deadline is created by this template.

13 Availability and changes

Software, internet connections and third-party APIs can be unavailable or delayed. Use the hotel's authorised fallback procedure and reconcile later. Do not keep submitting a form if the outcome is uncertain; first check the transaction history to avoid duplicate bookings, OTPs or financial entries.

These terms apply alongside module-specific instructions and permissions. A material change to these terms or the chat privacy model requires an updated version and renewed acceptance. The hotel's legal and employment obligations continue to apply even if software access is suspended or an entry is archived.

14 Acceptance

By selecting the acceptance checkbox, you confirm that you have read these staff-software terms and the privacy notice, including the Anonymous Chat identity-access clause. The software records the policy version, account and acceptance time. Acceptance does not give you access that MD has not granted or authorise actions outside your role.

If you do not understand these terms, ask hotel management before accepting. You do not have to post in chat to carry out your other permitted hotel work.

Back to Sign Up