Portfolios almost never standardize on one access control platform. They grow by acquisition, they inherit whatever the seller installed, and multi-site credential synchronization has to work across the result rather than against it.
By Nick Venuti, Senior Director of Product Marketing · September 2026 · 7 min read
Multi-site credential synchronization sounds like a solved problem until you look at an actual portfolio. Six buildings, five access control systems, three elevator manufacturers, and a card format history that nobody documented. The person who needs access to four of those buildings has four records, four card numbers, four enrollment dates and four separate offboarding processes, only one of which anyone will remember to run.
Why portfolios end up this way
Nobody designed it, which is why multi-site credential synchronization is an integration problem rather than a policy one. A portfolio acquires a building and acquires its access control system with it, along with a service contract, an integrator relationship and a reader estate that would cost more to replace than the building earns in a quarter. Standardizing sounds obvious in a board paper and stops being obvious the moment somebody prices the readers. So the estate stays mixed, and the operational cost moves to whoever has to make a person exist in all of it.
The variation is not only in the platform name. Card formats differ site to site, so a credential number that is a 35-bit Corporate 1000 in one building is a 37-bit format in another, and the same physical badge is not the same credential to both readers. Access level semantics differ too: one platform scopes them per partition, another applies them globally, and a third treats a floor as an attribute of the person rather than of the group. This is the detail that decides whether a multi-site credential synchronization project ships on schedule, and it is invisible in a feature comparison.
- HR platform, identity provider or directory service
- Role, department, home site and work locations
- Start date and last day of physical access
- The business rules that decide site membership
- Resolves one person across systems that hold them differently
- Applies the rule that decides which sites they belong in
- Writes into each site in that site’s own format and semantics
- Retires them in every site on a single event
- A different access control platform per site
- Site-specific card formats and reader technologies
- A different elevator manufacturer per tower
- Local access levels, partitions and floor groups
Synchronization is conditional, not wholesale. A person reaches a site because a rule put them there, and the rule is written once rather than argued per request.
What multi-site credential synchronization has to get right
Multi-site credential synchronization has to get two things right, and the second is where most in-house attempts stall.
A portfolio on three elevator makes has three interfaces, three floor models and three ways of expressing the same intent. braXos carries one entitlement into each of them, so somebody visiting a tower they are not based in reaches their floor without a local enrollment.
- Otis, KONE, Schindler, Mitsubishi, TK Elevator, Fujitec, MCE and more
- Destination dispatch and traditional hall-call in the same portfolio
- Floor rights derived from the entitlement, not kept per building
- 10+ elevator manufacturers integrated
- Mixed elevator estates treated as one population
Where braXos has the deepest bench. 10+ years of vertical access across multi-tower portfolios.
Matching a person across systems that spell them differently, hold different identifiers and disagree about which of them is current is the actual work. Once that resolution exists, writing into each platform is mechanical and everything downstream gets easier.
- Identity resolution across systems with no shared identifier
- Per-site card formats and credential numbering handled in the connector
- Site membership decided by rule, not by ticket
- A single departure retires the person in every building
- 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.
Four things this changes
Somebody based in one tower visits another in the same portfolio. The badge already works at that lobby and the elevator call is placed to the floor they are visiting, without a temporary pass or a call ahead to the security desk.
One tower runs destination dispatch, another runs traditional hall-call, a third is a different manufacturer entirely. The entitlement is written once and each interface is driven in its own terms, so the estate behaves as one system to the person holding the credential.
Someone changes role and work location in the HR system. Site membership is recalculated from the rule, access is added where it now applies and withdrawn where it no longer does, without anyone submitting a request for either half.
A single termination in the system of record retires the person across every site in the portfolio on the same event, rather than in five separate processes where the fifth is the one that gets missed.
How it runs in practice
Match one human being across systems that hold different identifiers, different name spellings and different opinions about which record is current. Every multi-site credential synchronization project stands or falls here, and it is the step most in-house attempts underestimate.
Site membership is derived from attributes the record already carries: role, department, home site, named work locations. Exceptions are handled by an override attribute rather than a side process that nobody maintains.
Composer provisions into each platform using that platform’s card format, access level model and partition structure, and Crescendo drives that tower’s elevator interface. Changes and departures travel the same path in reverse.
Integration detail
Copying everybody into every building is not multi-site credential synchronization, it is a liability. The rule that decides who belongs where is the product. The connectors are how it gets enforced.
Part of a wider ecosystem
A portfolio that has resolved one identity across its buildings has done the expensive part. The same resolution drives visitor management, parking, room and desk reservation and the print and vending estate at each site, and it is what makes a mobile credential practical across a mixed estate rather than in one flagship building. Each addition is configuration against a library rather than another integration project.
Bring a mixed estate under one identity
Tell us which platforms are in your portfolio and we will tell you what multi-site credential synchronization looks like across it, and what connects today. Or browse the connector library first.
Talk to us about your portfolioMore on the platform in the braXos connector library, or see the rest of the Symphony Series.
Visit us at www.braXos.com | [email protected]
