How it works
The portal never replaces the console or its policies. It reads the directory, lets each person change the things that are theirs, and writes every change back through the official API with an audit trail.
You create an API token in UniFi Access with the minimum scopes. The portal provides a connection profile for your console; you import it into your UniFi gateway, which connects to our service. We verify the console and test the connection. Nothing on the console changes and nothing is opened at your site.
The portal pulls the user list every few minutes: names, emails, which address group each person belongs to, and what credentials are on file. PINs and card secrets are never copied; only whether they exist.
A resident types the email the manager has on file and gets a 6-digit code. If the email is a user at one of your gates, they see that gate. No passwords, no accounts to create.
When a resident sets a PIN or adds a plate, the portal writes it to UniFi Access through the official API, confirms the result, and records who did what in the audit log.
Community managers decide whether residents may pair their own cards and on which readers, cap plates per household, and can see and change everything a resident can, including moving a plate, card or tag that was put on the wrong person or visitor account.
Architecture
Three roles
Anyone whose email is on a user record at one of the community's gates.
Managers or board members the community names. A manager can run more than one community.
The people who run My Community Gates.
Scope
My Community Gates is self-service software for a UniFi Access gate, plus support for using it. We do not install, maintain or repair gates, operators, readers, intercoms, cameras, hubs or networks; your community keeps its own gate service provider for that.
The requirements page lists what the console, the network and the gate hardware need.