Skip to main content

Approvals and notifications

Turn on approvals when someone should check each booking before it's confirmed, for example a clubhouse rental.

M
Written by Michael Bollinger

Turn on approvals when someone should check each booking before it's confirmed, for example a clubhouse rental. This article covers who gets asked, who can approve, how to approve or deny, and which emails owners and admins get along the way.

Before you start: You need to be an admin, or have Amenities write permission. See Give board members and staff access.

Turn on approvals

Approvals are set per amenity, in the Approvals card. In the Add amenity setup it's on the Availability step; on an existing amenity, open it and click Actions → Edit details.

The card says: "When required, a board member or manager approves each booking before it's confirmed."

  1. Set Approval required? to Yes.

  2. Under Send approval alerts to, choose who gets the approval email:

    • All admins (shown as Any admin once saved): every admin gets the email.

    • One person: only that person gets the email. The picker lists your admins.

  3. Click Save & apply (new amenity) or Save changes (existing amenity).

If your association uses the new Inbox, there's no picker. Send approval alerts to shows the current choice, Any admin to start, with a Manage in Notifications link, both in the setup and on the edit page. Click the link to change the person in a small dialog: pick someone under Who gets it, then save. The list has your admins, read-only admins and anyone you've given a module permission, so you can name a board member who isn't an admin. If nobody is picked, the email goes to every admin. Only admins can change this; others see "Only admins can change who gets notifications."

The amenity's About card shows the choice under Approval alerts go to: a name, Any admin, or "Nobody, no approval needed".

Tip: before you switch Approval required? back to No, approve or deny any pending requests. Otherwise they stay pending and drop off the Pending approvals count.

Who can approve

Anyone with Amenities write permission can approve or deny a booking: every admin, and any board member or manager you've given Write on Amenities. It isn't limited to the named person: naming someone decides who gets the email, not who may decide.

The person named under Send approval alerts to when the booking was made can also approve or deny it, even without Amenities permission. Without that permission they can't open the Amenities pages, so they decide from the Calendar (see below).

Approve or deny a booking

You can find pending requests in several places:

  • Pending approvals card on the Amenities page: click it to open All bookings filtered to pending requests.

  • The amenity's page: a banner says "You have 1 new request pending approval", and the Bookings card has a Pending approvals tab.

  • The "Booking Approval Required" email: its Review Request link opens the amenity's pending requests.

To approve:

  1. Click the booking to open Booking details. The timeline shows when it was requested and who was notified.

  2. Click Approve.

You see "Booking approved successfully". The booking moves to Upcoming. In the admin panel its status shows as Scheduled; the owner sees Confirmed.

To deny:

  1. Open Booking details and click Deny.

  2. In Deny booking request, enter a Denial reason (at least 3 characters). "The resident gets an email with this reason, unless they have turned off booking emails."

  3. Click Deny booking.

You see "Booking denied". The booking moves to Cancelled or declined with the status Rejected and your reason.

You can also use the Approve and Deny buttons in the Decision column on the Pending approvals tab or in All bookings.

On the Calendar, a pending booking on the Amenity bookings layer shows Waiting for approval. Click it to Approve or Decline it there. To decline, click Decline, enter a Reason (it's shared with the owner) and click Decline booking. Without a reason you see "Add a reason so the member knows why."

What approving does to the money

For a free amenity, approving confirms the booking and that's all.

For a fee-based amenity, the owner isn't charged when they book. When you approve:

  • A charge for the booking is added to the owner's unit account, due in 30 days.

  • The owner gets the approval email and a separate invoice email with a Make a Payment link.

Denying a booking doesn't create a charge. See Fees, payments, cancellation fees and refunds.

If nobody acts on a request

A pending request that nobody approves or denies by the end of the booked slot is rejected automatically, within about an hour of the slot's end time. Until then you can still approve it, even after the slot has started. Nobody is emailed when it's rejected: not the owner, not the admins. The booking shows as Rejected with no reason.

Check Pending approvals often, especially if alerts go to one person who may be away. If an owner says their booking vanished, look for it under Cancelled or declined.

Emails owners get

Owners get these emails about their own bookings. Most also go by text if the owner gets texts. Owners can turn off booking emails, with two exceptions: the "not approved" email and the invoice email are always sent if the owner has an email address.

When

Email subject

They book an amenity that needs approval

"Booking submitted for approval"

They book an amenity with no approval, or you book for them

"Booking Confirmed - {amenity}", with a calendar invite

You approve their request

"Booking Approved - {amenity}", with a calendar invite

A charge is created when you approve, or when you book a paid amenity for them

"Invoice for {amenity} Booking - Charge #{number}", with a PDF invoice

You deny their request

"Your booking request was not approved", with your reason

The booking is cancelled, by them or by you

"Your booking has been canceled"

The booking is moved, by them or by you

"Booking Rescheduled - {amenity}", with a calendar invite

Before a confirmed booking

"Booking Reminder - {amenity}"

Each confirmed booking gets one reminder. PayHOA sends reminders once a day, early in the morning (US time), for bookings that start in the next 24 hours. A booking made after that day's run gets its reminder about an hour before it starts instead. Pending bookings get no reminder.

Most associations can't change the wording of these emails. If your association uses the new Inbox, the booking emails are listed under Amenity bookings on the Emails tab in Settings, and you can edit them there. See Customize PayHOA's automatic emails.

Emails admins get

Admins get one email: "Booking Approval Required - {amenity}", when an owner books an amenity that needs approval. It goes to the person named under Send approval alerts to, or to every admin if that's Any admin.

Admins aren't emailed when:

  • an owner books an amenity that doesn't need approval;

  • an owner cancels or reschedules;

  • a pending request is rejected automatically.

To keep track of these, check All bookings or the amenity's Bookings card. See Manage bookings.

Troubleshooting

What you see

What to do

I didn't get the approval email

Check Approval alerts go to on the amenity's About card. If one person is named, only they get it. With Any admin, only admins get it, not board members with Amenities permission.

A former board member still gets approval emails

They're the named approver. Edit the amenity and pick someone else under Send approval alerts to (with the new Inbox, click Manage in Notifications). If they get "Clubhouse rental request" emails, those come from a Requests form, not from Amenities.

"Unable to approve booking. Please contact your administrator."

The time may no longer be free, or a fee-based amenity has no Deposit account. Check the amenity's Pricing section, then try again.

A booking request disappeared

It was rejected automatically because nobody acted before the booked slot was over. Look under Cancelled or declined.

"Enter a reason of at least 3 characters."

The Denial reason is required. Write a short explanation for the owner.

Related

Did this answer your question?