Floor-level access planning for connected buildings
Ubiquiti Elevator Access Control Solutions in Dubai, UAE
Control who may select protected floors, apply time-based permissions and manage credentials through UniFi Access. FourTeck helps organisations translate building requirements into a practical elevator-access architecture without assuming that every lift system, reader or control panel connects in the same way.
Start with the lift interface
Share the number of cars, controlled floors, elevator controller details, credential method and project location before finalising hardware.
Per UA-SK-Elevator hub design
Simplifies reader data and power planning
Assign users, locations and schedules
Elevator contractor approval is essential
Direct answer: what is a Ubiquiti elevator access solution?
It is a UniFi Access deployment that places an authorised credential step between a passenger and selected elevator floor buttons. A compatible reader identifies the user, the Access application checks the applicable policy, and the Elevator Hub enables the permitted relay outputs so the corresponding floor choices can be used. The solution should be considered by buildings that want centrally administered floor permissions alongside door access. Before proceeding, buyers must confirm the exact elevator interface, number of cars and floors, reader choice, credential type, emergency and fire-service behaviour, network availability, controller hosting and the responsibilities of the lift contractor, access-control integrator and IT team.
What the solution does
Ubiquiti’s Elevator Hub is designed to connect to in-elevator readers over PoE and authorise floor selection through relay outputs. The current Elevator Starter Kit identifies support for up to 18 floors and provides inputs that can be used for elevator car status, position, door state and emergency conditions. In practical terms, the system does not replace the elevator controller. It acts as an access-control layer that enables or disables permitted floor-button circuits according to configured user access.
Administrators can create access policies and schedules in UniFi Access, assign credentials to people and define where and when those credentials are valid. The operational benefit is centralised administration: a user’s door and elevator privileges can be managed within the same access platform, subject to the features available in the deployed console, application version, reader and hub.
Who should consider it
The solution may suit commercial towers, premium residential buildings, hotels, serviced apartments, clinics, educational campuses, private clubs, government offices and mixed-use developments. It is especially relevant where different groups need different floor rights, such as tenants limited to leased levels, employees assigned to departmental floors, residents granted access to their home level and shared amenities, or contractors restricted by schedule.
It is not automatically the right choice for every project. Buildings with proprietary elevator interfaces, complex destination-dispatch systems, high floor counts, strict life-safety integration, legacy wiring constraints or specialist regulatory requirements need detailed engineering review. A qualified elevator contractor should confirm how relay-based access control may be connected without affecting certified lift functions.
Business challenges and the response to each
Unrestricted floor movement
Apply credential-based floor permissions so a valid badge, mobile credential or supported access method is required before protected floors become selectable.
Frequent occupant changes
Update access centrally when employees join, tenants move, contractors finish or temporary permissions expire, instead of changing mechanical controls at every floor.
Disconnected door and lift systems
Use UniFi Access as a shared administration layer for supported doors and elevators, while keeping the elevator’s safety and motion control under its specialist system.
Weak audit visibility
Review access events through the platform to support security investigations and operational oversight, subject to retention settings and the deployed environment.
Core solution capabilities
Floor permission control
Map relay outputs to controlled floor selections and associate floor rights with user policies.
Scheduled access
Limit permissions by working hours, tenancy rules, visitor windows or defined operational periods.
Credential flexibility
Choose a compatible UniFi Access reader and supported credential methods based on user experience and project policy.
Central management
Administer identities, policies, schedules, devices and events from the UniFi Access application.
Solution-fit decision matrix
| Business situation | Relevant assistance | Scope dependency |
|---|---|---|
| One elevator car with up to 18 controlled floors | Review an Elevator Hub-based design and suitable reader | Actual relay wiring and lift-controller approval |
| Multiple cars serving the same floors | Prepare a per-car hub, reader, network and cabinet plan | Car wiring, travelling cable and controller topology |
| More than 18 protected selections | Engineering review for scalable architecture or alternatives | Do not assume multiple hubs can be combined without validation |
| Existing UniFi network and Access deployment | Extend policies and device management into elevator access | Console capacity, PoE budget, VLANs and software versions |
| Destination-dispatch elevator system | Joint review with elevator manufacturer and specialist integrator | Standard relay enablement may not meet the control logic |
Compatibility and responsibility notice
An elevator is a safety-critical system. Access control may only interface with approved circuits and must not interfere with braking, movement, levelling, door protection, fire recall, emergency operation, accessibility functions or rescue procedures. The elevator manufacturer or authorised maintenance contractor should identify the correct dry-contact, relay or interface points and confirm electrical ratings. The security integrator should document the Access Hub inputs and outputs, while the network team should provide stable PoE, switching, addressing and controller access. The building owner remains responsible for regulatory approvals and operating procedures. FourTeck can help define the technology scope, but the final installation method must be accepted by the relevant specialists and authorities.
A practical engagement and deployment journey
Requirement discovery
Record the number of lift cars, served floors, controlled floors, user groups, visitor process, operating schedules, credential preferences and existing UniFi environment.
Elevator interface review
Obtain controller drawings, relay requirements, car-top or machine-room locations, travelling-cable availability and written guidance from the elevator contractor.
Solution design
Select hub and reader models, plan PoE switching, controller hosting, network segmentation, enclosure, cable paths, credentials and access policies.
Quotation and responsibilities
Separate supply, network work, access-control wiring, lift interface, software configuration, testing, documentation and optional support in the bill of materials.
Installation and testing
Commission one controlled path at a time, validate fail states and emergency conditions, and test permissions for representative user groups and schedules.
Handover and operations
Provide drawings, port schedules, device names, policy logic, administrator roles, credential procedures, backup guidance and change-control responsibilities.
Policy-based floor access that reflects real occupancy
The main value of elevator access control is not the relay hardware alone. It is the ability to turn a building’s occupancy rules into manageable permissions. A corporate tower may allow employees to reach their leased floor, reception, parking and shared meeting levels. A residential building may grant residents their home floor plus amenities, while property staff receive broader rights. A hotel may need staff profiles that differ from guest access. UniFi Access policies and schedules provide the administrative framework for these distinctions, but the design must stay understandable to the people who will operate it every day.
Policy design should begin with roles rather than individuals. Create defined groups such as residents, facilities, cleaning, security, finance, contractor and visitor sponsor. Assign each group only the floors and time windows required. Individual exceptions should be limited and documented, because too many one-off rules make reviews difficult. Temporary access should have an expiry date, and dormant credentials should be removed or disabled. The building should also define who can approve changes and who can audit them.
Consider what should happen outside normal hours. Some floors may remain available to all authorised occupants, while sensitive areas require additional restrictions. Cleaning or maintenance teams may need narrow service windows. Emergency and life-safety behaviour must remain independent of ordinary access rules. A clear policy matrix signed by security, facilities and the relevant business owners makes configuration and acceptance testing much easier.
Reader and credential experience inside the elevator car
Reader choice affects both technical design and passenger experience. The device must fit the available panel or wall location, receive reliable PoE, remain reachable for maintenance and support the credential methods the organisation intends to issue. Depending on the selected UniFi Access reader and platform features, organisations may consider NFC cards, key fobs, mobile credentials or other supported methods. Exact functions should be verified against the current reader specification and application release before purchasing.
An elevator environment introduces practical constraints that are less common at a fixed doorway. Cab panels may have limited space. Decorative materials can affect mounting. Cable paths may pass through travelling cables or specialised lift wiring. Vibration, cleaning procedures, user reach and accessibility all matter. A reader with a display or camera may create different privacy, bandwidth and mounting requirements from a compact credential reader. The final choice should therefore be made with the elevator contractor and interior consultant, not only from a product photograph.
The user interaction should be obvious: present the credential, receive a clear acceptance or denial indication, then select an authorised floor. Signage may be needed for visitors or first-time users. Security staff should have a defined process for denied access, lost credentials and exceptional movement. The organisation should also decide whether one credential can be used across doors, gates, Wi-Fi or VPN through broader UniFi Identity workflows. Those options may improve administration, but they should be assessed for licensing, device compatibility and privacy policy before deployment.
Network, power and controller architecture
The Elevator Hub uses Ethernet for management and PoE++ for power, while its reader-facing ports can provide PoE+ within the published aggregate power budget. This architecture can reduce separate power supplies, yet it makes switch selection and power planning important. The upstream switch port must provide the required PoE class, the cable path must meet Ethernet standards, and the combined load of connected readers must remain within the hub’s output budget. Where the elevator car moves, the method of carrying network connectivity to the car must be approved by the lift specialist.
A dedicated security or access-control VLAN is often appropriate. Firewall rules should permit only the required communication between the hub, reader, UniFi console, management clients and any supported remote services. Administrators should avoid placing building-security devices on an unrestricted user network. Device naming should reflect site, building, lift bank, car and reader position so alarms and events can be understood quickly. Network monitoring should include switch port status and PoE consumption, while access administrators monitor device adoption and application health.
The UniFi console or hosting platform is another design dependency. Buyers should confirm that the chosen controller supports the current UniFi Access application and has suitable capacity for the overall device count. Backup, update and administrator-access procedures should be documented. Ubiquiti recommends keeping UniFi OS, the Access application and access devices current for new features and optimal operation, but updates in a live building should still follow change-control and testing. A maintenance window, configuration backup and rollback plan are prudent for critical sites.
Ideal environments and realistic use cases
Multi-tenant offices
Limit tenant employees to reception, parking, shared amenities and their leased floors while giving facilities and security broader operational rights.
Residential towers
Assign residents and household staff to relevant floors and common areas, with defined processes for guests, deliveries, move-ins and maintenance teams.
Hotels and serviced apartments
Support role-based staff movement and carefully scoped guest-floor workflows, subject to property-management and visitor-system integration requirements.
Healthcare and clinics
Restrict staff-only, laboratory, pharmacy or records levels while preserving emergency and accessibility procedures defined by the facility.
Education and training centres
Separate public, student, faculty and administration areas, with schedules that match class hours, events and maintenance periods.
Private business facilities
Control movement to executive, research, finance, data-room or archive floors where general building access should not imply floor access.
Operational and integration considerations
Access events are useful only when they are interpreted in context. An accepted credential indicates that the system authorised the relevant floor options; it does not necessarily prove that the person travelled to a specific floor, especially if several users are in the car. Buildings needing strict anti-passback, occupancy counting or destination tracking should define those requirements explicitly and confirm whether additional systems are necessary. Avoid assuming that a standard floor-button enablement design provides every feature associated with advanced elevator destination control.
Visitor handling deserves its own workflow. A receptionist may issue a temporary credential, a host may escort the visitor, or a separate visitor-management platform may be used. Any desired integration with intercoms, resident directories, mobile apps or property-management systems should be tested for the exact software version and device combination. Product-roadmap discussions or community examples should not be treated as guaranteed functionality. A proof of concept is advisable when a workflow depends on an integration that is not clearly documented in current official material.
Audit and privacy policies should define who can view access events, how long records are retained, how requests are handled and when logs are exported. Video-capable readers create additional privacy and storage considerations. Cybersecurity controls should include unique administrator accounts, multi-factor authentication where supported, least-privilege roles, protected management networks and a documented process for firmware and application updates. Physical security remains equally important: hubs, switches and termination points should be in controlled enclosures with labelled, serviceable wiring.
Questions to resolve before requesting a quotation
How many cars and floor selections?
Provide a schedule for each elevator car. The total number of building floors may differ from the number of buttons that require control.
What elevator controller is installed?
Share manufacturer, model, age, maintenance provider and any available interface documentation or approved access-control module.
Which credentials will users carry?
Confirm card technology, mobile-access expectations, visitor credentials and whether existing badges must be reused.
Where will the reader and hub be mounted?
Identify available space, cable route, enclosure, power, environmental conditions and maintenance access.
What happens during an emergency?
Document fire recall, emergency override, security release, power failure and manual operational procedures with the lift contractor.
Who owns each part of the project?
Assign responsibilities for elevator wiring, network, access configuration, credential enrolment, testing, approvals and ongoing support.
Procurement and evaluation checklist
☐ Exact number of elevator cars and controlled floors
☐ Current elevator manufacturer, controller and maintenance provider
☐ Approved relay or interface method for every car
☐ Required Elevator Hub quantity and spare strategy
☐ Selected reader model and mounting accessories
☐ Credential types, quantities and enrolment process
☐ UniFi console and Access application hosting
☐ PoE++ switching, cable paths and aggregate power budget
☐ VLAN, firewall and remote-management requirements
☐ Emergency, fire recall and fail-state behaviour
☐ Installation, configuration and testing responsibilities
☐ Drawings, labels, training and handover documentation
☐ Warranty guidance and regional product variant
☐ UAE availability, delivery coordination and vendor lead time
How FourTeck supports the buying process
FourTeck can help turn an initial requirement into a structured request for quotation. The process may include confirming whether the project is an elevator floor-access requirement rather than a destination-control requirement, reviewing the floor and car schedule, identifying suitable UniFi Access components, checking PoE and controller dependencies, and defining which work belongs to the elevator contractor. This preparation reduces the risk of ordering a hub or reader before the interface has been validated.
For organisations already using UniFi, FourTeck can discuss how elevator access may fit alongside the existing network, door access and physical-security environment. For new deployments, the consultation can cover the required UniFi console, switching, VLAN design, reader locations, credentials and administrator roles. Any bill of materials should clearly separate required components from optional mounts, enclosures, credentials, network equipment, installation labour and support services.
Buyers can review additional business technology offerings through the FourTeck product catalogue, discuss planning through the technology services team, or send project information through the FourTeck Dubai contact page. Company background is available on the FourTeck UAE profile.
UAE availability and project coordination
Contact FourTeck to confirm current UAE availability for the Ubiquiti Elevator Starter Kit, Elevator Hub, selected readers, credentials, mounting accessories and any required UniFi console or PoE switching. Availability may vary according to region, quantity, hardware revision and vendor lead time. A quotation should identify the exact part numbers and distinguish hardware supply from access configuration, network work and elevator integration.
For projects in Dubai, Abu Dhabi, Sharjah and Ajman, FourTeck can coordinate requirement review and commercial planning after receiving the site details. Delivery and project scheduling should only be discussed after the bill of materials, destination and implementation responsibilities are confirmed. Where installation is requested, the scope should state whether FourTeck is providing access-control configuration, network preparation, testing support or coordination with the appointed elevator contractor. No party should connect to a lift controller without the appropriate technical approval.
GCC Availability
FourTeck can assist organisations evaluating Ubiquiti elevator access control for projects across the Gulf region, including the United Arab Emirates, Saudi Arabia, Kuwait, Qatar, Bahrain and Oman. Regional planning should begin with the destination country, exact elevator arrangement, required hub and reader quantities, preferred credential method, UniFi hosting environment and expected deployment schedule. FourTeck can support requirement review, component and license guidance where applicable, quotation coordination, delivery planning, configuration scope and discussions around installation responsibilities. Product availability, regional variants, vendor lead times, service visits and project schedules can differ by country and quantity. Elevator standards, local approvals, power arrangements and the maintenance contractor’s interface policy may also affect the design. Buyers should therefore provide controller documents, site location, number of cars, controlled floors and any support expectations before commercial terms are finalised. For Kuwait-related coordination, the FourTeck Kuwait technology channel may also be relevant.
Africa Availability
Organisations planning controlled elevator access in African commercial, residential, hospitality or institutional buildings can contact FourTeck for product evaluation and regional procurement guidance. The review can cover the Elevator Hub, compatible readers, credentials, PoE switching, controller hosting, accessories, configuration scope, support expectations and renewal or lifecycle planning for related services. Fulfilment depends on the destination, model and quantity, shipping arrangements, vendor lead time, power and regulatory conditions, installation responsibilities and the local elevator contractor’s approved interface. Buyers should share the destination country, lift manufacturer, number of cars, controlled floors, project timeline and whether remote configuration or local coordination is expected. FourTeck does not assume local inventory or guaranteed onsite coverage. For selected regional discussions, organisations may use the FourTeck Africa portal and the dedicated Kenya technology resource to begin requirement clarification.
Related products and services to evaluate
UniFi Access readers
Select a reader by credential method, display needs, indoor suitability, mounting space, PoE demand and desired user interaction.
UniFi consoles
Confirm a supported hosting platform for UniFi Access with sufficient capacity and a maintainable update and backup process.
PoE switching
Plan PoE++ input, reader output budget, VLANs, uplinks, surge protection and resilient power appropriate to the site.
Door access control
Extend common identity and policy administration to supported lobby, office, plant-room and amenity doors where appropriate.
Configuration services
Define site adoption, device naming, user roles, policies, schedules, credential enrolment, event review and administrator handover.
Network and security review
Assess switching, controller access, firewall rules, remote administration, backups and operational cybersecurity for the access platform.
Why businesses contact FourTeck
Elevator access projects cross several disciplines, and many procurement problems arise when the hardware is selected before the responsibilities are clear. Businesses contact FourTeck for help clarifying the requirement, reviewing suitable Ubiquiti components, structuring a bill of materials, identifying network and PoE dependencies, checking credential requirements and defining the configuration scope. FourTeck can also help buyers prepare the questions that must be answered by the elevator manufacturer or maintenance company.
The objective is practical procurement clarity rather than unsupported promises. A useful quotation should name the model, quantity, accessories, delivery destination and services, while identifying assumptions and exclusions. It should not imply that relay wiring, software configuration, elevator engineering and life-safety approval are the same task. By separating these elements, project owners can compare proposals fairly and appoint the right specialist for each part of the implementation.
Frequently asked questions
Does the Ubiquiti Elevator Hub control elevator movement?
No. It is intended to authorise floor-button selection through relay outputs. The elevator controller remains responsible for movement, doors, levelling, recall and safety functions.
How many floors can one Elevator Hub control?
The current UA-SK-Elevator specification lists 18 relay outputs and support for up to 18 floors. Confirm the exact button and relay schedule for each elevator car.
Can the system be used in a high-rise with more than 18 floors?
It requires engineering review. Do not assume that hubs can simply be combined for a single car. Share the elevator topology and floor count so a suitable architecture or alternative can be assessed.
Which UniFi Access reader should be installed in the car?
The choice depends on credential type, mounting space, PoE budget, display or camera requirements and software compatibility. Confirm the exact reader before ordering.
Is a recurring license required for UniFi Access?
Ubiquiti describes UniFi Access as license-free. Optional identity, hosting or related services may have separate conditions, so the complete workflow should still be reviewed.
Can existing employee cards be reused?
Possibly, but card technology and security format must be compatible with the chosen reader and enrolment method. Provide sample credential details for review.
Who should connect the hub to the lift controller?
The work should be coordinated with the authorised elevator contractor or specialist approved for the installed lift system. Access wiring must follow the approved interface method.
What information is needed for a quotation?
Provide the project location, number of cars, controlled floors, elevator manufacturer and controller, reader preference, credential type, existing UniFi equipment, quantity and required services.
Can FourTeck assist with configuration and installation planning?
Yes, the requested scope can include component selection, UniFi Access configuration, network planning, testing guidance and coordination boundaries. Elevator-controller work remains subject to specialist approval.
Is the Elevator Starter Kit currently available in Dubai?
Availability can vary by quantity, region and vendor lead time. Contact FourTeck to confirm current UAE options and a project-specific quotation.
Plan the access policy before ordering the hardware
Send FourTeck the lift schedule, controller details, car count, controlled floors, credential preference and required project scope. The team can help prepare a suitable component list and identify questions for the elevator contractor.