Knowledge Center

Tenant Mobile Credentials Without an IT Project on Either Side

Tenant mobile credentials without an IT project on either side

Symphony Series

The base building owns the turnstiles and the elevator bank. Each tenant owns its own people. braXos Symphony gives the tenant somewhere to add them, and gives the building a credential that already knows which floors to open.

By Nick Venuti, Senior Director of Product Marketing  ·  September 2026  ·  8 min read

Use case
Tenant onboarding into a base building
Entry path
Portal first, integration when the tenant is ready
braXos products
Symphony, Composer, Crescendo

Most multi-tenant buildings issue tenant mobile credentials the same way they issued plastic ten years ago. A tenant emails a spreadsheet of new starters to property management, someone retypes the names into the base building access control system, and the new employee collects something at the security desk two days later. The credential technology moved to the phone. The workflow did not move at all. braXos Symphony changes the workflow first, and it does not ask the tenant to build anything to get there.

Where tenant onboarding actually breaks

The problem in a base building is not technical, it is organizational. The building has one access control system. It has thirty tenants, and those tenants run thirty different HR systems, or none at all. Property management sits in the middle as a queue, retyping names that already exist somewhere else and answering emails about whether someone’s access has been set up yet.

Every mobile credential program that stalls, stalls here. The technology is ready. The reader estate is ready. What is not ready is a workflow that lets a tenant with four employees and no IT department get those four people into the building without asking anyone for a project plan.

Who adds the person
The tenant
  • A tenant administrator, scoped to their own suite
  • New starters, contractors, visiting colleagues
  • No HR system, no API work, no integration project
braXos platform
Symphony
  • Checks the request against what the lease entitles that tenant to
  • Issues the credential into the base building access control system
  • Records the change with a timestamp, a source and the change detail
  • Hands floor authorization to Crescendo for the elevator bank
The building
Doors, turnstiles, floors
  • Base building access control system, whichever one it is
  • Lobby turnstiles and suite doors
  • Destination dispatch and traditional hall-call elevators

Direction of travel is left to right. The tenant never touches the building’s access control system, and property management never retypes a name.

Two paths to tenant mobile credentials

Symphony supports both, on the same platform, at the same time. A building does not have to choose one for the whole estate. The tenant that wants a portal login this afternoon and the tenant that wants its identity provider wired straight through can both be served in the same lobby.

Vertical transportation
The floors come with the credential

braXos reads the badge event at the turnstile or the lobby kiosk and places the elevator call automatically. Floor authorization comes from the same groups that drive door access, so a tenant taking a second floor does not trigger a second enrollment.

  • Destination dispatch and traditional hall-call alike
  • 10+ elevator manufacturers already integrated
  • Floor rights follow the access group, not a separate list
  • A suite expansion is an entitlement change, not a re-badge
  • One credential across a multi-tower portfolio

Where braXos has the deepest bench. 10+ years of vertical access across multi-tower portfolios.

Credential lifecycle
Issued, changed and revoked from one screen

The tenant administrator invites someone by email. That person enrolls on their own phone. The credential is provisioned into the base building access control system, and it can be suspended or revoked from the same screen it was issued from.

  • Email invitation and self-service enrollment, no security desk visit
  • HID Origo and the credential technologies the building already runs
  • Activation and expiration dates on every profile and credential
  • Revocation takes effect without collecting anything back
  • Provisioning activity recorded with a timestamp, source and change detail

The same layer reaches everything else. 200+ pre-built connectors, 50+ of them for access control.

Why this matters

A mobile credential program is usually sold on the phone and lost on the paperwork. The business case assumes people stop carrying plastic. What actually happens is that plastic stays in circulation for two more years because the onboarding path for mobile is harder than the one for cards, and the security desk is still the fastest route to a working credential. Making the portal path genuinely faster than the desk is what moves adoption.

The second thing it changes is who owns the error. When a tenant types its own people into Symphony, the tenant owns the spelling, the start date and the leaver notice. Property management stops being the transcription layer and starts being the entitlement layer, which is the job the lease actually gives it.

Four tenant workflows this covers

Day one for a new tenant hire

The tenant administrator adds the new starter on Friday with a Monday start date. Monday morning the credential activates, the turnstile reads it, and the elevator call to their floor is placed before they reach the bank. Nobody met them at a desk.

A suite expansion onto a second floor

The tenant signs for floor 14 alongside floor 12. The base building updates the entitlement once. Every credential in that tenancy picks up the new floor, and no one re-enrolls or re-badges to get it.

A fit-out crew with an end date

Eighteen contractors are added with an expiration date that matches the works program. Access stops on that date whether or not anyone remembers to close it out, and the credentials do not have to be chased down afterwards.

A departure at four in the afternoon

The tenant administrator revokes the person in Symphony. There is nothing to collect at the door, the credential stops working at the turnstile and at the elevator, and the change is recorded with its source.

How the portal path works

01
The building scopes the tenancy

braXos creates the tenant in Symphony and the base building defines what that tenant may grant: which doors, which floors, which hours. The tenant administrator can work freely inside that boundary and cannot step outside it.

02
The tenant invites the person

Name, email, start date, and the access the lease allows. The invitation goes out immediately. No file transfer, no ticket to property management, no waiting for the next batch.

03
The person enrolls and the building updates

The credential is delivered to the phone and provisioned into the base building access control system through Composer, with floor authorization passed to Crescendo. Changes and revocations follow the same path.

Integration detail

Who administers
Base building sets entitlement. Tenant administrators manage their own population inside it.
braXos products
Symphony for identity and credential management, Composer for the access control integration, Crescendo for vertical access.
Credential technologies
HID Origo mobile credentials, plus the card formats and reader technologies already deployed in the building.
Access control platforms
50+ access control connectors. The tenant workflow is identical regardless of which one the base building runs.
Vertical transportation
10+ elevator manufacturers, destination dispatch and traditional hall-call.
Deployment
braXos cloud or on-premise Composer. No software for the tenant to install and nothing for the tenant to host.

The portal is not a lesser version of the integration. It is the on-ramp that gets a building to mobile while the integration conversation is still being scheduled.

Part of a wider ecosystem

The same connective layer that carries a tenant credential to the turnstile and the elevator already reaches visitor management, parking, secure print release, room and desk reservation, and smart vending. A building that starts with tenant onboarding does not have to start again to add any of them, because the identity is already resolved and the entitlement already exists. That is the argument for a connector library rather than a set of point integrations.

Minutes
from invitation to working credential
Zero
retyping between tenant and building
200+
pre-built connectors
50+ of them access control

Start tenants on mobile without starting a project

Talk to us about the Symphony portal for your base building, or browse the connector library to see what is already built for the systems you run.

Talk to us about your base building

More on the platform in the braXos connector library, or see the rest of the Symphony Series.

Visit us at www.braXos.com | [email protected]

Share:
Facebook
Twitter
LinkedIn