How To: AA Sister Sites

We manage a property with two unique Yardi codes. Accordingly, we've set up two distinct entries in CMW. They wish to integrate Alloy Access (AA) for community access. How should this be configured in AA?

Alloy Access Sister Sites Definition

I describe this scenario as "Sister Sites," where two properties, possibly adjacent or within the same structure, have individual PMS codes. Each PMS code gets it’s own CMW property & these sites intend to share access to certain common area facilities via Alloy Access. Real-World Example: Site A and Site B, located across from each other and under the same ownership, operate in unison. Site A has a gym to which Site B's residents need access. The goal is for residents at Site B to use identical credentials (PINs, Fobs & Mobile) for the gym at Site A and the communal doors at Site B.

Implementation Best Practices

Avoid creating two separate Alloy Access sites. Instead, establish a single Alloy Access site for both Site A and Site B. Add all of the doors, controllers & cloud bridges to one site Generate multiple API clients for this unified AA site, one for each CMW group.

Client Downsides of this approach

The Alloy Access intercom contact list currently (as of Dec 19, 2023) includes all residents at the site, resulting in some from Building A appearing on Building B's intercom. A solution is planned. Property staff can view events and temporarily control doors in both buildings. If the site has elevators the number of ALs could become a lot to manage