- What problem does this solve?
- Every PIN reset, plate change and fob pairing today is a phone call or an email to the manager, then someone logging in to the UniFi console. The portal lets residents do those things themselves, safely, while the manager keeps full visibility and the final say.
- Do we have to replace our gate hardware?
- No. If your gate runs on UniFi Access, the portal connects to what you already have. If it runs on something else, the portal cannot connect to it; see the requirements page.
- Do you maintain or repair the gate?
- No. We provide the self-service software and support for using it. Installing, maintaining and repairing the gate, its operator, readers, intercom, cameras, hubs and network stay with your gate service provider, as today; keep that contract. A reader that stops reading or a gate that sticks is a call to them, not to us.
- Does the portal ever open the gate?
- No. The API token we ask for has no door-unlock scope, so the portal cannot open a gate even if someone wanted it to. It only manages credentials and people.
- Can residents give themselves access they should not have?
- A resident can only act on their own user record and, for household features, on their own address group. Gate access itself is granted by the access policy on the address group, which only the manager and the console control. A resident cannot create a user outside their address, assign a card that belongs to someone else, or change anyone else's PIN.
- How do we remove someone who moved out?
- The community manager opens the address, disables the person, and removes them. The portal disables the Access user, detaches them from the intercom entry and deletes the user, and records who did it. Residents cannot remove other people; that always goes through the manager.
- What does a typical installation look like?
- Residents and managers use the portal in a browser or on their phones. The portal runs in our cloud and reaches your UniFi Access console over a secure, private connection from your UniFi gateway, so nothing at the community is exposed to the internet. At the gate, a UA Hub Gate drives the operator and connects the UniFi reader or intercom for PINs, cards and the app; a Protect camera adds license plates; and a Retrofit Hub brings legacy Wiegand devices such as toll-tag or remote receivers into Access. The Requirements page has the diagram and a table of which reader gives residents which feature. All of it is installed and maintained by your integrator, not by us.
- Which readers and credentials does it work with?
- Whatever your console already accepts: PINs on any UniFi keypad or intercom, license plates through a Protect camera with plate recognition, NFC cards and fobs on UniFi readers, toll-tag transponders and gate remotes through Wiegand readers on a UA Hub Gate or Retrofit Hub, and the UniFi Identity Endpoint app for mobile unlock and intercom calls. Each credential type the gate supports becomes a self-service feature for residents; the rest simply does not appear.
- We have several gates on separate consoles. Does that work?
- Yes. Each console is a “gate” in the portal and a resident who exists on more than one sees all of them under one login. Vendor PINs can be set at every gate of the community at once.
- We manage several communities. Can one person run them all?
- Yes. A community manager can be added to any number of communities and switches between them inside the management console. Residents of one community never see another.
- Where does the data live and who can see it?
- On a server we run in Google Cloud in the United States, in a database that holds the directory copy (names, emails, address group, what credentials exist), the audit log and encrypted console tokens. PIN values and card secrets are never stored. Platform administrators at My Community Gates can see every community for support; community managers see only their own.
- What happens if the portal is down?
- The gate keeps working exactly as before: every credential lives on your console, not with us. Residents simply cannot make changes until the portal is back, and the manager can always use the UniFi console directly.
- How long does setup take?
- Usually under an hour per console, done together: you create the API token on the console, we connect the gate in the portal and hand you a connection profile, you import it into the gateway and add one firewall rule, and the gate shows connected. Then import your resident list from a four-column spreadsheet (address, email, first name, last name) and the portal creates every address and person on the console. Communities are typically live for residents within a week.