Spintly

Designing Role-Based Elevator Access in Multi-Tenant Buildings with OptiSpaces

12 min reading time

Updated on July 23, 2026

Share this article

Table of Contents

The Real Problem in Multi-Tenant Buildings

If you’ve ever worked in a single-tenant office, access control feels almost invisible. Everyone belongs to the same company, works on similar floors, and access rules are fairly uniform for everyone. Once someone enters the building, there’s rarely a question of where they can go.

But that simplicity disappears the moment you step into a multi-tenant building.

Now, the same building is shared by multiple organizations. Each tenant has its own employees, its own workspace, and its own boundaries. At the same time, the building itself includes shared areas like lobbies, parking zones, or common facilities.

So access is no longer just about entering the building, it’s about controlling movement inside it. And this is where things start getting complicated.

Because without a structured approach:

  • Employees from one tenant may access another tenant’s floor
  • Visitors may move beyond their designated areas
  • Permissions can overlap without anyone realizing it

In such setups, even a small misconfiguration can lead to real security gaps.

Why Role-Based Access Matters

In many buildings, elevator access is still treated as an open system: “If you’re inside, you can go anywhere.”

But in a shared environment, that doesn’t hold up. It can lead to significant security issues. That’s why access needs to be controlled based on context, not just entry.

In OptiSpaces, elevator access is designed around three key factors:

  • Tenant (organization): Which company the user belongs to
  • Role: What kind of user they are (admin, employee, visitor)
  • Permissions: Which floors they are allowed to access

Access varies by role like employees use their floor, admins multiple floors, and visitors get limited access. 

How OptiSpaces Connects the Pieces

What makes this work is how OptiSpaces connects different parts of the system together.

It brings together:

This means:

  • Every user is mapped to a tenant
  • Every tenant operates within defined limits
  • Every user’s access is tied to their identity

So access decisions are always part of a structured system.

Setting up the Foundation

The elevator first needs to be brought into the system. In OptiSpaces, this means:

  • The elevator is added as an access point
  • This setup is done by a Partner
  • Only after this is in place can admins start assigning floor-level permissions

This makes the elevator part of the same access system.

Identity-Based Access (Not Device-Based)

One of the most important design decisions in OptiSpaces is this: Access is tied to identity, not the credential

Each user:

  • Has a digital identity
  • Belongs to a tenant
  • Is assigned specific floors

Access is granted based on who the user is in the system.

For example, you might have one company operating on floors 2 and 3, while another operates on floors 5 and 6. Even if users from both companies use the same type of credential, their access is completely different because it’s tied to who they are in the system.

This keeps access consistent and easier to manage.

Designing Access Through Roles

Once identity is defined, the next layer is roles. Because even within the same organization, not everyone needs the same level of access.

For example:

  • An employee typically only needs access to their own office floor.
  • Someone in an admin or managerial role might need to move across multiple floors. 
  • A visitor should only be allowed into specific areas, often for a limited time.

Instead of treating everyone the same, the system adjusts access based on what a person actually needs to do. So access stays aligned with real-world responsibilities.

Handling Shared vs Restricted Spaces

Think about spaces like lobbies, parking, or common amenities, these are meant to be accessible across tenants. But at the same time, office floors or internal areas need to stay restricted to specific organizations.

OptiSpaces handles this by combining floor-level permissions with tenant-aware access control. Every floor is mapped, and access is assigned based on both the user’s identity and the tenant they belong to.

So in practice:

  • Shared floors can be made accessible across multiple tenants (when allowed)
  • Private floors remain restricted only to the relevant tenant

This ensures shared access doesn’t break tenant boundaries.

How Admins Actually Manage This

Based on your system, Admins can assign elevator access:

  • While creating a new user
  • From an existing user profile
  • Directly from the elevator (access point) interface

They can:

  • Select the elevator
  • Choose specific floors
  • Assign or remove permissions instantly

Admins can assign access to multiple users and update permissions anytime.

What keeps everything controlled is that not everyone can make these changes. Only Super Admins and Site Admins have the ability to assign or modify elevator permissions ensuring control remains centralized and secure.

Real-Time Access Updates

Buildings don’t stay the same for long. Teams grow, people change roles, and sometimes entire tenants shift floors or expand into new spaces.

In traditional systems, this would require:

  • Reconfiguration
  • Manual updates
  • Possible downtime

But in OptiSpaces:

  • Permissions can be updated anytime
  • Changes reflect immediately
  • No hardware-level rework is needed

Visibility and Accountability

In multi-tenant setups, visibility is important. OptiSpaces provides visibility into who accessed which floors and when, ensuring accountability without added complexity.

Making a Complex System Feel Manageable

Managing elevator access across multiple tenants can get messy really fast. Without a clear structure, permissions start overlapping, boundaries blur, and small mistakes can turn into real security concerns.

What OptiSpaces does well is bring order to all of this.

Instead of relying on manual tracking or scattered rules, everything is defined in a structured way:

  • Tenants define boundaries
  • Roles decide what kind of access is needed
  • Identity ties each user to the right permissions

And once this is set, the system takes care of enforcing it. There’s no constant need to double-check or fix things manually. The right person gets to the right floor without friction or confusion.

And as buildings scale, that kind of clarity is what keeps operations smooth behind the scenes, instead of turning into chaos.

Explore more blogs

Secure Your Property Today.

Connect with a Spintly Expert within 24 hours.

Get in touch