Questions? Start here.

Veyra Stays brings building and unit management, short-term bookings, day visitors, guest registration, QR access, maintenance and controlled incident review into one platform. It is built for property managers, reception, security teams, owners and letting agents.

Contact support@veyrastays.com or +27 87 997 0000 to discuss your buildings, units, entrances and visitor workflows. Pricing and hardware are quoted for your requirements; no current fixed price is published in this help centre.

Yes. A unit can have multiple permanent parking bays and linked storage rooms, plus floor, garage location and lockbox details. Create or link these resources on the unit before allocating booking parking. Multiple permanent bays do not mean every booking screen supports multiple simultaneous vehicle allocations.

Yes. Directory relationships include owners, tenants, managing agents, building managers, security officers, caretakers and emergency contacts. Link contacts to the building or the relevant unit. A directory contact is not automatically a login account.

Admin has global building and operational access, including the current Access Logs and Audit Logs, but cannot manage users. Super Admin manages users and protected API integrations. Company Administrators can administer their own company users and assigned portfolio, without unrelated building access.

Yes. Owner and letting-agent accounts operate within explicitly assigned units, their relevant contacts, bookings and day visitors. They do not receive building-wide security administration. Select a building, then a unit, and Add each authorised unit to the account.

Yes. A management-company workspace can show its company name and logo. Company Administrators manage company-scoped users and the company portfolio. Operational menus also depend on the assigned features; company membership does not automatically enable every function.

An authorised user administrator can open Users, select the account, and use Reset password & resend login. This creates a new temporary password; the existing password is not recovered. Passwords require at least eight characters, a letter, a number and a special character. Provider acceptance is not a guarantee of inbox delivery. Never enter passwords into this chat.

Each recorded party member has a unique pass. Booking door permissions apply to the group, while pass status is individual. Staff can use Email QR passes for active passes with email addresses, or print a pass. Do not share one lead guest pass among the whole party.

Yes. Staff can create self-registration invitations for existing bookings, or dispatch a blank booking form after choosing the building/unit and a valid client email. The client fills in their details away from the desk. Staff then review the record and complete the access setup. Sending to a tablet and sending an email are separate actions.

Booking channels and manual verification states are available. Choosing Airbnb or Booking.com does not connect to that provider. Automated reservation verification requires a separately approved provider or channel-manager integration; it is not established in this implementation.

Use Day Visitors → Register Visitor, select the destination building and unit, record the person, reason and same-day access window, and obtain authorised door permissions. A vehicle registration can be recorded. Returning visitors can reuse their profile for a new timed visit without removing old visit history.

Open View details. Revoke access cancels the visit/pass. Revoke and recapture preserves the old record and creates a fresh capture invitation. Owners and agents are limited to their assigned units and cannot grant building security permissions. Contact reception if you need a door allocation corrected.

Photo omission is permitted in some self-registration/testing paths, while a staff capture path may still require it. Biometric enrolment requires an appropriate photo and authorisation. Day-visitor email invitations and view/print passes are established; automatic email of every completed day-visitor pass with rules is not confirmed. Check the deployed workflow with support.

Possible reasons include an unknown or revoked pass, the wrong building, a door not assigned to the booking/visit, an access window that has not started or has ended, or an inactive parent record. Ask authorised reception staff to check the pass, visit/booking and door. This assistant cannot check a real pass or override access. Do not paste QR tokens into chat.

Bookings and day visitors have time-based list tabs. Future starts are Upcoming; ended or inactive records are Expired; other active-window records are Current. List classification is not itself an access decision. Reception should check the actual record and pass when investigating an access question.

Booking pass emails include an inline QR image and an attached QR PNG, with saved building rules below. When a bay is allocated, the message instructs guests to use only that bay and warns about clamping. Save rules using headings and separate bullet lines. Updated rules affect new emails, not messages already sent.

Bookings support lockbox details and issued equipment such as remotes, tags, keys and access cards, including serial/reference, deposit and return notes. Deposit statuses include Held, Refunded and Forfeited. This is an operational register, not a payment gateway; recording a refund does not execute a bank transaction.

Authorised users open Management → Maintenance and report a problem with its building, location, category, priority and description. Staff can edit the item, add timestamped notes and move through Reported, Acknowledged, In Progress, Waiting, Resolved, Closed and Archived. Each note records its author. Use site emergency procedures for urgent hazards rather than relying on a ticket or chat.

Authorised staff record factual incidents for human review. A protected identity-reference match is not a biometric fingerprint, proof of misconduct, government identity verification or an automatic blacklist. A no-match is not a clearance certificate. This assistant cannot search, disclose or decide a real person’s incident history.

The product includes restricted access and privacy-oriented controls, but these do not by themselves establish legal compliance or certification. Operators need appropriate policies and professional advice for their processing and sharing arrangements. Do not submit IDs, photographs, passwords, QR passes or personal guest details in this public chat.

The project includes a Raspberry Pi reader for the Newland NLS-FM430 and a reception capture kiosk. The reader checks QR access with the server and displays console decisions. The kiosk is a Python application that opens hosted forms in a kiosk browser. Relay hardware, displays, networking and physical commissioning must be scoped separately.

A pilot connector supports person/photo and timed-access synchronisation, tested historically with the DS-K1T342MFWX-E1. Residents and timed visitors have different access policies. Photos, authorisation, door permissions, connectivity and safe commissioning are required. Camera sync logs are not physical entry logs, and this is not a general compatibility guarantee or an established iVMS integration.

A Super-Admin-provisioned partner API supports guest checks and incident submissions/amendments, with named apps, credentials, explicit scopes and building assignments. Reports enter central human review; partners cannot self-substantiate or make automatic admission decisions through this API. Contact support for the developer manual and approval process.

No. An access decision does not prove physical passage. A normal shared door may let several people through after one scan. Reliable anti-passback or individually controlled passage is not provided by the current ordinary-door arrangement and requires a separate physical design.

No. This is an AI product-help assistant using published guidance, not an operator console or a staffed live-chat service. It cannot read your private records, reset passwords, unlock doors, check a guest or promise that a staff member is online. Contact support@veyrastays.com for account-specific help.