Skip to content
English
  • There are no suggestions because the search field is empty.

Troubleshooting: Received Alert for Member Booking from Another Location

A team member receives an alert that a member from another Studio location has booked a day pass or room at their site. These steps outline how to confirm and register the visiting member correctly.

Why This Happens (Root Cause)

The new Yardi interface now sends automatic alerts when a member books at a location other than their home site.
This helps onsite teams prepare for cross-location visits and maintain accurate security registration.

What to do (Action Steps)

Step 1 — Register the visiting member

  • Log into CloudGate and register the visiting member for building access.
    Why: This ensures security staff are aware of all active visitors from other Studio locations.

Step 2 — Note booking hours

  • Cross-location bookings are valid only between 9:00 AM and 5:00 PM.
  • If the member requests extended hours, handle on a case-by-case basis

Why: Standard hours ensure proper onsite coverage and member support.

Step 3 — Completion

Once the member is registered in CloudGate, no further action is required.

Quick Summary

  • Root Cause: Automatic alert triggered for cross-location bookings in Yardi.
  • Fix: Register visiting member in CloudGate
  • System Behavior: Bookings from other locations trigger notifications for 9–5pm visits to ensure security and team visibility.

Maven

Maven should trigger this article when any of the following are mentioned:

  • “I got an email about a member from another location booking here.”
  • “What do I do when a visiting member books space at my site?”
  • “Why am I getting alerts for bookings from other locations?”

Tags

cross-location booking, member visit, yardi alert, cloudgate, onsite registration, building access