AI CITY TECHNOLOGIES

Guest passes and short-stay access

From a one-off visit to a short stay, stay in control of guest access.

A pass for your guest

A resident creates a guest pass with a validity period and usage limit. The guest opens the link in a browser or uses a PIN or QR at a compatible entrance; the host can revoke the pass before it expires.

An access link the guest opens in a browser

Send the guest a pass link that they can open in their phone’s browser.

Guest PIN or QR at compatible entrances

At a compatible entrance, guests can use the assigned code or QR within their pass permissions.

Validity periods and usage limits

Limit the pass to the required validity period and number of uses for the visit.

Name passes to recognise each guest

Name each guest pass so you can tell invitations apart when managing several visits.

Revoke a pass early

Revoke the pass before its scheduled expiry if the visit is cancelled or access is no longer needed.

Opening result on the guest page

For a supported door, the guest page shows execution progress and the returned result rather than treating a sent command as an opened door.

Organise a short stay

In buildings with short-stay access enabled, owners can register a visit with its property, guests, allowed doors and dates. Guests receive an invitation or activation code, and the host can check whether access has been activated.

Choose the apartment, guests and permitted doors

When preparing a visit, select the property, guests and entrances they may use.

Set arrival and departure dates

Set the arrival and departure period to keep guest access within the visit dates.

Share an invitation or activation code

Share the invitation or code guests use to activate the access prepared for them.

See activation progress

Check whether an invited guest has activated access or still needs to complete that step.

Available in buildings with the service enabled

Short-stay visit management is available in buildings where management has enabled the service.

A defined stay, a clear end

A short-stay visit can include up to two guests and last up to twenty days under the service’s rules. It can be extended within the permitted limits or cancelled early, and guest access ends when the visit expires.

Up to 20 days and two guests per stay

Arrange each visit within the service limits of up to two guests and twenty days.

Extend within the permitted duration

If a guest stays longer, extend the end date only within the service’s permitted limits.

Revoke one guest or the whole stay

Cancel one guest’s participation or end the entire visit when needed.

Access ends when the stay expires

The guest’s temporary permission ends at the specified time rather than remaining active indefinitely.

Management can review stays

Managers can review short-stay visits to oversee temporary access within their building.

A controlled limit on new stays

A host can create up to ten stays within a rolling thirty-day period under the service’s rules.

Later anonymisation of guest data

After the stay ends and the configured retention period passes, guest personal data has a defined anonymisation process.

Just what a guest needs

Short-stay guests receive only the entrances allowed for their visit and intercom calls available under the occupancy arrangement. Building finances and community chats remain within the resident area; guest access also ends if the host loses the underlying authorization.

Access only to granted entrances

Guests can use only the doors selected for their visit, without general access to other entrances.

Intercom calls can follow the activated guest’s occupancy

Under an active visit and its occupancy conditions, relevant intercom calls can be routed to the guest.

Access stops if the host loses entitlement

If the host’s underlying access right ends, the related guest access also stops working.

Building finances and community conversations remain within the resident workspace

Temporary guest access does not open residents’ finance sections or community conversations.

Availability depends on the user’s role, enabled services and compatible equipment.