• Solutions for Every Building, Every Stakeholder

    URBI is the first Building OS powered by HERO AI. Whether you manage properties, own them, or operate them day to day, URBI transforms complex, disconnected workflows into a single, intelligent platform that drives efficiency and builds stronger communities.

    Role Benefits

    • For Property ManagersStreamline operations and enhance tenant satisfaction with centralized management tools.
    • For Building OperatorsSimplify daily tasks and maintenance with intelligent automation and workflow management.
    • For OwnersMaximize ROI and property value with comprehensive oversight and analytics.
    • For Finance TeamsClose faster with double entry books, trust accounting, and reconciliation that runs nightly.
    • For BusinessesConnect with building communities and expand your service offerings.

    Building Benefits

    • Residential BuildingsSimplify living with one app for bookings, packages, payments, and community updates.
    • Commercial BuildingsStreamline operations, vendors, and compliance while giving tenants a frictionless experience.
    • Education BuildingsManage facilities, visitors, and compliance for safer, smarter, more connected campuses.
    • Senior LivingAnswer families around the clock, publish life enrichment once, and see every community on one screen.
  • One Platform. Smarter Buildings.

    URBI centralizes daily operations and adds AI intelligence to transform complexity into clarity.

    Products

    • URBI KoreThe central hub where managers, owners, and staff run building operations in one place.
    • URBI KonnectA marketplace that connects buildings with trusted vendors, services, and community events.
    • URBI AccountingAI consolidation, invoices and receipts processed by AI, books pre reconciled before month end. In Beta.
    • URBI AIOne intelligence across URBI. HERO answers your team's questions, Arthur answers your community's calls, texts, and emails 24/7.

    Features

    • Operations & Workflow
    • Amenities & Booking
    • Events & Ticketing
    • Communication & Community
    • Payments & Transactions
    • Data & Compliance
    • HERO AI Intelligence
    • IoT & Hardware Integration
    • Community Experience
    • Accounting (In Beta)
    View All
  • Customers
    • All ResourcesGuides, support, and customer stories in one place
    • Help CenterGuides and answers for every part of URBI
    • BlogWhy URBI works the way it does
    • ReleasesEvery update we ship, in plain language
    • System StatusHow every part of URBI is running right now
    • About UsLearn about our story and mission
    • MilestonesHow URBI got here and where it is going
    • CareersWe're HiringJoin our growing team
    • FAQStraight answers about URBI, HERO and Arthur
    • ContactGet in touch with us

Schedule a Demo

  1. Help Center
  2. /Operations
  3. /Requests for Access
  4. /Requests for Access: Overview

Requests for Access: Overview

What a request for access is, when to use one, and where it lives in Kore.

Last updated August 26, 2026

Operations
  • Approvals: decide expenses, board votes and RFPs in one place
  • Board Decisions: overview
  • Confirming packages, and what a refused package means
  • Document sharing
  • Finding the packages for one home
  • How to approve expenses and RFPs in Approvals
  • How to create a decision
  • How to create a time limited public link
  • How to generate the PDF report
  • How to run a vendor RFP through Board Decisions
  • How to share a file or folder
  • How to upload with drag and drop
  • How to vote and finalize a decision
  • How to vote on board decisions in Approvals
  • Operations
  • Troubleshooting
  • Troubleshooting document sharing
  • When a scanned package needs a look
    • Add Assignees to a Service Ticket
    • Attach a Vendor to a Service Ticket
    • Convert a Service Ticket to a Task (and make sure it stays visible)
    • Create a Service Ticket
    • Documents on a Service Ticket
    • Finding a Ticket: Search and Filters
    • How the Emergency Number Is Chosen
    • How to Convert a Service Ticket into a Board Decision
    • How to Reassign Work When Removing a Team Member
    • How to Set the Emergency Line
    • Notes on a Ticket, and What the Resident Can See
    • Service Ticket Statuses Explained
    • Service Tickets: Glossary
    • Service Tickets: Overview
    • Service Tickets: Troubleshooting
    • Set Up Recurring Service Tickets
    • The History on a Ticket: What It Records
    • The Tabs on a Service Ticket, Explained
    • Troubleshooting
    • What Residents See When They Create a Ticket
    • What's New in Service Tickets
    • Who Can Do What on a Service Ticket
    • Add Assignees to a Task
    • Create a Task
    • Organize Tasks with Categories, Projects, and Labels
    • Set Up Recurring Tasks
    • Access Request Statuses Explained
    • Choosing Who Receives a Request for Access
    • How to Send a Request for Access
    • Mandatory vs Request: Which One to Send
    • Recording an Answer on Someone's Behalf
    • Requests for Access: Glossary
    • Requests for Access: Overview
    • Requests for Access: Troubleshooting
    • Reschedule Requests: How They Work
    • Sending a Reminder for a Request That Has Not Been Answered
    • What the Recipient Sees and How They Answer
    • Awarding the Work
    • Comparing Proposals
    • How to Invite Vendors to an RFP
    • Putting an RFP to a Board Vote
    • Requests for Proposal: Glossary
    • Requests for Proposal: Overview
    • Requests for Proposal: Troubleshooting
    • RFP Statuses Explained
    • What a Vendor Sees and How They Submit a Proposal
    • Asset Impact: Overview
    • Asset Impact: Troubleshooting
    • Cancel Bookings or Block New Ones
    • Closure Statuses Explained
    • Confirming a Closure, and Why Scheduling Is Not Enough
    • How to Close an Amenity for Scheduled Work
    • What Happens to Bookings and Money When You Close an Amenity
    • How to view and add a vendor's expenses
    • Requesting Completion, and Technician Notes
    • Vendor Billing Tab: FAQ
    • Vendor Billing Tab: Overview
    • What a Contractor Sees on a Work Order
    • Set Maintenance Schedules for Assets
    • Track Equipment and Warranties
All collections

On this page

  • The two kinds of request
  • What the recipient gets
  • What your team gets
  • One detail worth knowing up front
  • What is in this set

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.

The two kinds of request

There are two, and the difference matters to the person receiving it:

  • Request asks permission. The recipient can approve, deny, or (if you allow it) propose a different date.
  • Mandatory gives notice. The recipient can only acknowledge that they have seen it. Entry is happening either way.

Choosing between them is covered in Mandatory vs Request: Which One to Send.

What the recipient gets

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.

What your team gets

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.

One detail worth knowing up front

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.

What is in this set

  • Mandatory vs Request: Which One to Send
  • How to Send a Request for Access
  • Choosing Who Receives a Request for Access
  • What the Recipient Sees and How They Answer
  • Access Request Statuses Explained
  • Reschedule Requests: How They Work
  • Sending a Reminder
  • Recording an Answer on Someone's Behalf
  • Glossary: What Each Term Means
  • Troubleshooting

Was this article helpful?

Related articles

Operations

Requests for Access: Glossary

Plain definitions of every term on the Access Requests tab and the form.

Read
Operations

Requests for Access: Troubleshooting

The problems that actually come up, and what to do about each one.

Read
Operations

Access Request Statuses Explained

What each status on the Access Requests tab means, including the one that surprises people.

Read
Operations

Choosing Who Receives a Request for Access

Units, occupant types, custom groups, and how to avoid sending a notice to the wrong half of a building.

Read
All Operations articlesAsk the URBI team
URBI

URBI is the Building OS, founded in Calgary in 2023. One platform with HERO AI built in, running thousands of units for property managers, condo boards and owners.

Solutions

  • All Solutions
  • For Property Managers
  • For Building Operators
  • For Owners
  • For Finance Teams
  • For Businesses

Building Benefits

  • Residential Buildings
  • Commercial Buildings
  • Education Buildings
  • Senior Living

Products

  • All Products
  • URBI Kore
  • URBI Konnect
  • URBI AI
  • URBI Accounting (Beta)

Company

  • About URBI
  • About Us
  • Milestones
  • Reviews
  • FAQ
  • CareersWe're Hiring
  • Contact

Resources

  • All Resources
  • Help Center
  • Blog
  • Releases
  • System Status
  • FAQ
  • For AI assistants

Compare

  • Compare Us to Residential
  • Compare Us to Commercial
  • Compare Us to K-12

Legal

  • Security & Privacy
  • Terms & Conditions
  • Terms of Service for Konnect

© 2026 URBI. All rights reserved.

Privacy PolicyTerms of Service

Schedule a Demo