What a request for access is, when to use one, and where it lives in Kore.
Last updated
A request for access is how your team tells the people living or working in a unit that someone needs to come inside, and gets a recorded answer back. It replaces the paper notice under the door and the phone call nobody remembers making.
Every request for access belongs to a service ticket. You do not create one on its own. You open the ticket for the work being done, go to its Access Requests tab, and send the request from there. That link is deliberate: the answer needs to sit next to the work it is about, so whoever does the job can see who said yes.
There are two, and the difference matters to the person receiving it:
Choosing between them is covered in Mandatory vs Request: Which One to Send.
Each recipient gets a notification with a private link to a page showing your property name, the unit, what the access is for, and the scheduled date and time. They answer on that page. No app download, no password, no account.
The Access Requests tab on the ticket lists one card per unit, each showing where that unit stands: waiting, approved, denied, or asking for a different date. Above the list, a counter shows how many were sent and how many have come back. You can send a reminder to a unit that has not answered, and record an answer yourself if someone replies by phone instead of using the link.
The access details, the date, and the start and end times are stored on the ticket, not on each unit's individual request. Every unit you send that ticket's request to sees the same details and the same window. If you change them, you change what every recipient sees, including the ones who already answered. Sending genuinely different windows to different units means using separate tickets.