How building entry systems create access logs

An access event is different from a person entering

ButterflyMX's technical documentation distinguishes access attempts and successful unlocks from historical intercom call attempts. It says permissions limit administrators to managed buildings and tenants to their own activity. Read an event's result and type before treating it as evidence of physical entry. ButterflyMX: access attempts, calls and permission scope

The administrator guide describes timestamps, access points, tenant names or units, release status and methods, with related photos in its intercom examples. It also lists scheduled opening as a method that needs no person to trigger it. A door-release row therefore needs context. ButterflyMX: administrator call and door-release records

Call and visitor records can connect to a unit

The privacy policy describes property-access information, potentially including a name, date, time and photo or video, tied to a unit and viewable by its tenant and property management. It says the company processes tenant and visitor information as a service provider to property owners or managers. Confirm the actual building's configuration and roles. ButterflyMX: property data, optional contacts and processor role

A visitor pass has a schedule and a history

The visitor-pass help says property management must enable the feature. It distinguishes scheduled, recurring and single-use passes, with door and expiration choices. For the described Video Intercom pass use, it says a timestamped photo is available for review in the mobile app for 365 days. That statement is about the described photo feature, not every building record or backup. ButterflyMX: visitor-pass scope and photo availability

Directory visibility is a separate setting

ButterflyMX documents removing a resident's name from the intercom directory while keeping app access. The effect is specific: visitors cannot call that resident from the entry panel, while available app features such as opening doors and visitor passes remain. Directory hiding should be read within that scope. ButterflyMX: directory visibility and call consequences

Removing access does not necessarily remove past events

The vehicle-management help says editing or removing a vehicle does not change that plate's existing Door Releases history. Resident editing depends on the property enabling it; otherwise administrators make the change. A current access permission and an earlier event record are different things. ButterflyMX: vehicle access and retained history

The administrator guide also describes requesting PDF reports by email and filtering records by dates, status, method and access point. Ask the property which people can review or export records, how records are interpreted and how retained exports are handled. ButterflyMX: administrator call and door-release records