A single-tenant building has one access control problem. A multi-tenant building can have several, and they can compound each other in ways that are rarely apparent until the system is live and a tenant is on the phone asking why their staff can access a floor they are not supposed to.
Multi-tenant access control is one of the more technically demanding applications in commercial property management. Get it right and it operates invisibly – tenants access what they need, cannot access what they should not, and the building manager has complete oversight without managing individual tenant requests. Get it wrong and the consequences range from frustrated tenants and embarrassing security incidents to genuine data protection liabilities.
Here is what property owners, asset managers, and building managers need to understand before specifying or procuring an access control system for a multi-tenant environment.
The fundamental challenge: one system, multiple independent organisations
In a single-occupier building, access control operates within one administrative boundary. The security team manages credentials, defines access levels, and runs reports. There is usually a single data controller, one set of policies, and one team accountable for the system.
In a multi-tenant building, the physical infrastructure is shared. The access control server, the door hardware, the network, but the data is not. Tenant A’s employees, access histories, and movement records are entirely separate from Tenant B’s. The building manager needs to see everything. Each tenant needs to see only their own data. Neither tenant should be able to see the others.
Achieving this on a single platform requires careful architectural design. Most enterprise access control platforms like Lenel OnGuard, Genetec, Gallagher, C-Cure 9000 support multi-tenant configurations through segmented database structures, role-based administration, and partitioned reporting. Configuring them correctly is a design and commissioning skill, not simply a software feature. Specifying that a system “supports multi-tenancy” without verifying that the integrator has delivered it in a comparable environment is a risk.
Credential management at scale
In a multi-tenant environment, credential management is the daily operational challenge. Employees join. Employees leave. Tenants expand into additional floors or sub-let part of their space. A new tenant takes over from one who has departed. The access control system needs to handle all these events cleanly, quickly, and without administrative overhead falling on the building management team.
Modern access control platforms manage this through integration with HR and Active Directory systems where tenant credential issuance and revocation can be automated based on employment status changes. Mobile credentials where an employee’s access card is their smartphone, managed through an app significantly reduce the physical administration burden and eliminate lost card replacements as a recurring cost.
The building manager’s role should be confined to managing the shared infrastructure, i.e. lobby turnstiles, car park barriers, roof terraces, common areas, rather than processing individual tenant credential requests. A well-designed system makes that boundary clear. A poorly designed one collapses it.
What happens at lease end
The tenant departure scenario is where multi-tenant access control systems frequently reveal their weaknesses.
When a tenant vacates, every credential associated with their occupancy must be revoked. Every employee card, every visitor credential issued under their tenancy, every integration with their HR system or Active Directory. If this process is manual, it is slow, error-prone, and dependent on the departing tenant providing accurate data about which credentials are active.
Automated offboarding, where the system revokes all tenant credentials simultaneously on a specified date, without manual intervention, is a basic capability requirement for a multi-tenant environment. Verifying that the proposed system handles this reliably should be a specific evaluation criterion in any procurement process.
Common areas and shared infrastructure
The access control specification for common areas in a multi-tenant building is frequently underspecified. Lobbies, lift lobbies, meeting rooms available to multiple tenants, car parks, roof terraces, and service areas all require access control that reflects their shared status without compromising the privacy of individual tenants.
Time-based access rules where common areas are accessible to all tenants during business hours but require specific credentials outside those hours are a standard requirement that most platforms handle well. The complexity arises when tenants have different business hours, when access to meeting rooms needs to be bookable and tracked, or when a common area is adjacent to a restricted area and the physical layout creates an antipassback problem.
These are specification questions, not product questions. The right integrator will identify and address them during the design phase. The wrong one will discover them during commissioning.
Mobile credentials and the tenant experience
The commercial property market’s move toward premium tenant experience has made mobile credentials (where a smartphone replaces a physical access card) increasingly central to access control specifications for new developments and refurbishments.
Mobile credentials eliminate lost card administration, allow access level changes to be pushed to a device instantly rather than requiring the employee to visit a reception desk, and integrate with the visitor management and smart building platforms that premium tenants increasingly expect as standard.
The implementation model matters. Some mobile credential systems require a dedicated app that must be installed and managed on each employee’s device which can create IT governance questions for tenants with strict device management policies. Others, including Apple Wallet integration, operate through the native wallet functionality of the employee’s smartphone, removing the app management question entirely. Specifying which approach is appropriate for a given tenant mix is a design decision that should be made early.
Common questions about access control reviews
An access control review often uncovers outdated permissions, inactive user credentials, integration issues, ageing hardware, firmware that requires updating, and opportunities to improve security, compliance and day-to-day management.
Yes. A review can highlight vulnerabilities such as excessive user permissions, unsecured common areas, outdated software, weak credential management and gaps in how different security systems work together.
Multi-tenant buildings experience frequent changes in occupancy, staff and access requirements. Regular reviews help ensure permissions remain accurate, tenant data stays protected and the system continues to meet operational and compliance requirements.
Not necessarily. Many reviews identify opportunities to improve the performance of an existing system through software updates, configuration changes, improved integrations or operational improvements. Replacement is usually only recommended where hardware is no longer fit for purpose or supported.
Most commercial buildings should review their access control system annually, or whenever there are significant changes such as new tenants, office reconfigurations, building refurbishments or updated compliance requirements.
What to ask your integrator
Before appointing an integrator for a multi-tenant access control project, four questions are worth putting directly:
Can you show us a reference site where you have delivered multi-tenant access control on the same platform you are proposing for this building? References from comparable environments are the most reliable indicator of capability.
How is tenant data segregated in the proposed architecture, and who can access which data under what circumstances? The answer should be specific with a description of the database structure and the role-based access model.
How is tenant offboarding handled? The answer should describe an automated process, not a manual one.
How does the system handle credential management if we need to change platform or integrator at contract renewal? Vendor lock-in where the credential data is held in a proprietary format that cannot be exported is a risk that property owners rarely consider until they are facing a contract dispute.
Evolution designs and delivers access control systems for multi-tenant commercial environments across the UK, Ireland, Netherlands, and Norway. If you are specifying or procuring a system for a multi-tenant building, we would welcome a conversation about the design considerations specific to your property.
Learn more about our commercial real estate security solutions or get in touch with Evolution by clicking the button below.
