Gate Intercom Handover: Who Answers, Who Can Open, and Who Removes Old Access?

The directory is part of the operating system

An intercom handover is incomplete if a resident can answer a call but the property cannot safely change recipients or remove obsolete access. Treat the directory and permission model as part of the installation.

A Reddit condominium planner wanted two phones per unit and optional viewers, while avoiding shared accounts and unwanted notifications to other residents. Those are specific administration and routing questions. The post asks what works; it does not verify a supported configuration or current capacity.

Separate caller routing from entry authorization. A phone receiving a visitor call is not necessarily the administrator account, and a local code can remain active after a phone is removed from a directory.

Source: UniFi condominium intercom: two phones per unit, directory and permissions

Separate recipients from administrators

UniFi’s current call documentation supports directory entries with designated receivers and sequential call groups on covered readers. Receiver schedules control ordinary recipients’ call notifications; UniFi documents that Door Attendants still receive calls outside those schedules, with separate muting controls in the Access mobile app. Verify the exact reader, software and remote-access requirements instead of assuming every phone added to a project receives the same functions.

The Door Attendant role is broader, with monitoring and control abilities; UniFi directs intercom deployments to its current Call Receiver workflow. Do not give every resident broad administration merely to make a call ring. Define the minimum supported role, the doors it covers and any unavoidable visibility or permission limits.

Source: Ubiquiti: doorbell call methods, directory and receivers · Ubiquiti: Door Attendant permissions and current receiver roles

Illustrative scenario: the resident changes phone numbers

Imagine the gate still calls an old number after a resident moves out, while a shared keypad code remains unchanged. The hardware may be working perfectly, but the handover process failed. The property needs an update and revocation workflow that does not depend on the original installer remembering a private account.

Test a new directory entry and a deliberately expired test credential using authorized procedures. Verify each resident’s normal phone behavior, including missed calls and the intended fallback recipient. Do not record private numbers in public project documentation.

A call-receiver schedule and an access schedule are different records. Confirm both the directory destination and every credential associated with a departing person. Where temporary access is supported, test expiry and revocation on the installed system; deleting a displayed name alone is not proof that its other credentials stopped working.

Source: Ubiquiti: Access policies and schedules · Ubiquiti: visitor schedules, expiry and revocation

Make the ongoing obligations visible

Document subscription ownership, renewal responsibility, support contacts, secure recovery, and change procedures. Keep pricing conditional on current vendor terms; historical forum prices are not a procurement quote.

Acceptance should include the complete visitor interaction, directory update, temporary access expiration, and removal of a test user. Keep gate-safety and operator verification separate but coordinated. The finished system should be maintainable by authorized property staff without sharing one unrestricted administrator password.

Put it into practice

A decision table to keep handy