Requests for Access: Glossary
Plain definitions of every term on the Access Requests tab and the form.
Last updated
Definitions for the words that appear on the Request Access form, the tab, and the page recipients see.
Access request
A single notice to a single unit asking for, or giving notice of, entry. Sending to twelve units creates twelve access requests, each tracked and answered on its own.
Request type
Either Request, which asks permission and can be approved, denied, or rescheduled, or Mandatory, which gives notice and can only be acknowledged.
Access request details
The free text explaining what the access is for. It is stored on the ticket and shown to every recipient of that ticket's requests.
Access window
The date plus the start and end times during which someone may arrive. It is a window, not an appointment, and it is set in the property's own timezone. Like the details, it lives on the ticket and is shared by every request sent from it.
Allow recipients to reschedule
A toggle on the form. When on, recipients of a Request can propose a different date instead of only approving or denying.
Occupant type
The kind of person recorded against a unit. The available types depend on the property type, so a residential building, a commercial property, and a campus each present their own vocabulary. Used to decide which people in a unit get notified.
Custom group
A saved audience you maintain yourself, usable as the recipient list instead of picking units one at a time.
Requested
Status. Sent, and nobody has answered yet.
Accepted
Status. Approved, or, for a Mandatory notice, acknowledged.
Rejected
Status. The recipient denied access.
Pending
Status. The recipient proposed a different date and your team has to decide. It means waiting on you, not on them.
Acknowledge notice
The only answer available on a Mandatory notice. It confirms the recipient has seen it and understands access will be granted at the scheduled time.
Reminder
A repeat notification for an unanswered request, containing the same link. Always sent deliberately by a member of your team, never automatically.