Fix BuildingLink Access Control Not Syncing With Resident Records

Access control data usually doesn’t sync to resident records in BuildingLink because the access control integration is not fully connected, the matching fields (unit, resident name, email, external ID) don’t line up, or the sync is blocked by permissions, timing, or duplicate/archived records. Even when everything “looks correct,” the most common cause is a mismatch in how residents are identified between BuildingLink and the access system.

 

What “sync” means (simple)

 

• BuildingLink stores resident profiles (people) and units (apartments).
• The access system stores credentials (fobs/cards/mobile keys) and often ties them to a person record.
• Sync works only if both systems agree on who the person is and which unit they belong to.

 

The most common reasons it fails

 

• Integration not enabled for the building: Some properties have BuildingLink active but access control sync is not turned on, not licensed, or not configured per-building.
• Wrong mapping: The integration may require a specific match like unit number format (e.g., “1203” vs “12-03”), building code, or a unique resident identifier.
• Duplicate residents: Two profiles for the same person (one created by staff, one from portal invite) causes the access record to attach to the “other” profile.
• Resident status blocks sync: Archived, moved-out, future move-in, or “inactive” residents may not receive access updates.
• Email/phone mismatch: If the access platform uses email or phone as the key, a typo or different email prevents linking.
• Permission limits: The integration user/API account may lack rights to read residents or write access credentials.
• Sync is not real-time: Many systems sync on a schedule; changes may take hours, or require a manual “push/pull.”
• Partial data: Resident is missing unit assignment, move-in date, or required fields, so the record is skipped.

 

What to check in BuildingLink (quick checklist)

 

• Confirm the resident is assigned to the correct unit and not duplicated.
• Check resident status: active/current occupant, not archived, dates make sense.
• Standardize unit formatting: match exactly what the access system expects.
• Verify contact fields: email/phone spelled correctly if used for matching.
• Look for integration settings: confirm the correct access vendor is selected and connected for that property.

 

If the user already meets all requirements and it still won’t sync

 

• Force a re-link: remove the credential from the access system person record, then reassign after confirming the correct BuildingLink resident profile is the only active one.
• Check integration logs: look for “skipped,” “no match,” “duplicate,” or “permission denied.”
• Test with a brand-new resident: create one clean profile with a simple unit number; if that syncs, the issue is data mismatch on existing records.
• Confirm direction of sync: some setups only pull from access to BuildingLink (or the reverse). If it’s one-way, the “missing” updates are expected.
• Ask support to verify the unique key: request the exact matching rule (email, unit+name, external ID) and whether any records are stuck in a queue.

 

When to contact BuildingLink or access control support

 

• Multiple residents affected or new residents never sync.
• Logs show API/auth errors, permission issues, or repeated “no match” despite correct data.
• You need the vendor to reset mapping, rebuild the sync index, or change the matching key.