Access Logs — Spot GuestView Entry Opens and Always See the Phone
What changed: Keyless GuestView Entry opens are now easy to tell apart in your Access Logs. They previously showed up with a generic “Mobile” source and no phone number; now they carry their own “GuestView Entry” source label, and the visitor’s phone number always appears on the row — even when the visitor has a name on file.
Where to find it: CM sidebar > Access Logs (the “Source” column and the “User” column).
What you’ll see: GuestView Entry rows read “GuestView Entry” in the Source column instead of “Mobile,” and the visitor’s phone number appears as smaller, muted text just beneath their name in the User column. Other opens (app, NFC, API, access code, video call) are unchanged.
What you need to do: No action needed.
Who this affects: Community Managers
Community Messenger — See a History of Messages You’ve Sent
What changed: The Community Messenger page now keeps a running history of every message you’ve broadcast to your members, so a sent message no longer disappears once it’s delivered.
Where to find it: CM sidebar > Community Messenger (the “Sent Messages” log appears below the message box).
What you’ll see: Under the compose box, a “Sent Messages” list showing each broadcast with the date and time, who sent it, and the message text — newest first. Right after you send a message, the log refreshes to include it. Longer histories page in with a “Load More” button.
What you need to do: No action needed.
Who this affects: Community Managers
GuestView Entry — Set the Hours Keyless Entry Works
What changed: You can now restrict GuestView Entry to specific days and times per gate. Add as many availability windows as you need; outside them, the “Get me in” option simply doesn’t appear to visitors. Each window applies in the gate’s own local timezone, and a gate with no windows stays available any time (unchanged).
Where to find it: CM sidebar > GuestView > Settings tab > “Available Hours” (appears under the eligible-gates list once GuestView Entry is on).
What you’ll see: An “Available Hours” section with an “Add window” button. Adding a window lets you tap the days of the week, set a start and end time, and check which of your eligible gates it applies to — all eligible gates are checked by default, and if you only have one eligible gate it’s checked automatically. Saved windows list back grouped by day/time with a chip for each gate, and a remove button. A note reminds you that times apply in each gate’s local timezone.
What you need to do: No action needed — leave a gate with no windows and it stays available any time. Add windows only when you want to limit the hours.
Who this affects: Community Managers, Guests
GuestView Change Log — See Who Changed What
What changed: GuestView now keeps a 30-day history of every change made to your GuestView and directory settings, with who made each change, what changed, and when.
Where to find it: CM sidebar > GuestView > new “Change Log” tab.
What you’ll see: A table of recent changes — When, Who, Gate, Action, and Details — covering the GuestView Entry toggle, eligible gates, availability windows, directory viewing, view mode, curated directory, privacy, access codes, short codes, terminology, and directory exclusions.
What you need to do: No action needed — the log fills in automatically as settings change.
Who this affects: Community Managers, Nimbio Admins
GuestView Entry — Let Visitors Open Gates With a Phone Number
What changed: A new opt-in “GuestView Entry” feature lets a visitor who holds no key open an eligible gate after verifying their phone number. You control it per community and choose exactly which gates allow it. Every entry attempt — successful or not — is recorded in a new filterable log with the phone number, the visitor’s name (once known), the gate, the time, and the result.
Where to find it: CM sidebar > GuestView > directory settings (the “GuestView Entry” master switch and the “Eligible Latches for GuestView Entry” picker), and a new “Entry Log” tab on the GuestView page with a success/failure filter.
What you’ll see: A toggle to enable GuestView Entry for your community, a checklist to pick which gates allow it, and an entry log table (Time, Phone, Name, Gate, Result, Reason) you can filter to successes, failures, or all.
What you need to do: Turn on GuestView Entry and check the gates where you want to allow it. Nothing else is required — the log fills in as visitors use it. Scan-only gates automatically require the visitor to tap the gate’s NFC tag, so entry only works when someone is physically present.
Who this affects: Community Managers, Guests
Curated GuestView Directory — Show Only the Members You Choose
What changed: GuestView has a new “Curated Directory” mode. Normally your public directory lists every member of your community by default; with Curated mode on, it starts empty and shows only the specific members you hand-pick, so you can feature a front desk, a leasing office, or a small set of contacts instead of everyone.
Where to find it: CM sidebar > GuestView > Settings tab > “Curated Directory” toggle.
What you’ll see: A “Curated Directory” switch at the top of Directory Settings. Turn it on and a searchable member list appears just below, each member with a checkbox — check the ones you want listed and they appear in your directory immediately; leave the rest unchecked and they stay hidden. A running count shows how many are selected, and the Live Preview updates as you go. If a member has personally opted out of the directory, they remain hidden even when selected — a member’s own privacy choice always wins. Turn the toggle back off and your directory returns to listing all members as before.
What you need to do: No action needed unless you want a curated directory — turn it on and pick your members.
Who this affects: Community Managers, Guests
Homes Page Respects Your Custom Terminology
What changed: Two more spots on the Homes page now use your community’s chosen word for “Home” when you’ve customized your terminology: the empty-state message shown when there are no homes yet, and the “Allow New Members to Request Home” toggle.
Where to find it: CM sidebar > Homes (labeled with your chosen term).
What you’ll see: If you’ve renamed homes to, say, “Unit,” an empty list now reads “No Units” instead of “No Homes,” and the request toggle reads “Allow New Members to Request Unit.” Communities that haven’t customized their terminology continue to see “Home” and “Homes” exactly as before.
What you need to do: No action needed.
Who this affects: Community Managers
Refreshed Accept Member Screen
What changed: The screen for accepting a pending member into your community got a visual refresh and a couple of usability fixes. The keys-to-assign list is now searchable and scrolls within its own area, and the home selector respects your community’s custom terminology.
Where to find it: CM sidebar > Members > Pending tab > select a pending member.
What you’ll see: A cleaner modal with a member summary card (name, phone, or a clear “no confirmed phone number” note), a bordered “Keys to Assign” section with a search box that now scrolls to the matching key instead of only highlighting it (so a match further down the list is no longer hidden below the fold), a home selector labeled with your community’s chosen term (for example “Select Unit” if you renamed homes to “Unit”), and a tidier date section for the move-out / expiration date.
What you need to do: No action needed.
Who this affects: Community Managers, Nimbio Admins
Name Your Members and Homes — New Settings Page
What changed: A new “Settings” page lets you choose what your community calls its members and their groupings, so the app speaks your community’s language. Instead of everything saying “Resident” and “Home,” you can pick terms like “Tenant,” “Owner,” “Employee,” “Suite,” “Unit,” or “Office” — chosen from a curated list your Nimbio admin set up for your property type, or typed in as your own custom term — and pick an icon to go with each.
Where to find it: CM sidebar > Settings > Terminology & Icons.
What you’ll see: Two pickers — one for what members are called, one for what their groupings are called. Each offers a dropdown of ready-made options (with a “Custom…” choice for your own wording), a live preview icon, and an optional “Use a different icon” toggle that opens an icon gallery. Save, and your chosen words and icons appear throughout your community view — the sidebar, member and home pages, directory preview — and in your public GuestView directory.
What you need to do: Optional. If you do nothing, your community keeps showing “Resident” and “Home” exactly as before. Visit Settings whenever you’d like to tailor the wording.
Who this affects: Community Managers
Reconnect Fix — No More Stuck “Connecting…” Screen
What changed: Fixed a bug where the community-manager site could get stuck on the “Connecting…” screen and never recover after the browser tab had been left in the background for a long time. This builds on the earlier “handles network interruptions and idle tabs more gracefully” work — the full reconnect that was supposed to fire after a long idle wasn’t actually running, so the page could hang instead.
Where to find it: Anywhere in the app — this is the connection screen shown before any page loads. Most noticeable after leaving a tab idle and coming back later.
What you’ll see: Returning to a tab that has been backgrounded for a while now reliably re-establishes the connection and drops you back into the app, instead of hanging on “Connecting…” until you manually reload.
What you need to do: No action needed. (If you previously worked around this by reloading the page, you no longer need to.)
Who this affects: Community Managers
“View Children” No Longer Errors Out
What changed: Fixed a bug where the “View Children” button on a member’s details could appear for community managers who don’t have permission to view child keys — and crash to an error screen when tapped. The button now only shows when you actually hold that permission, and viewing a member’s child keys works reliably.
Where to find it: CM sidebar > Members > select a member > member details > “View Children.”
What you’ll see: If you have permission to view child keys, “View Children” opens the list as expected. If you don’t, the button simply isn’t shown anymore — so there’s no way to hit the error.
What you need to do: No action needed.
Who this affects: Community Managers
Assign-a-Tag Wizard — Clearer Gate Buttons
What changed: In the wizard that assigns an NFC tag to a gate, the final step where you choose which gate now presents each gate as a distinct, tappable button rather than a plain text row.
Where to find it: Tap a not-yet-set-up NFC tag > “Assign this tag” > pick community > gate selection step.
What you’ll see: Each gate appears as a bordered, rounded card with a gate icon on the left and an arrow on the right, and it highlights when you hover or tap — making it obvious that each one is a button that advances the wizard.
What you need to do: No action needed.
Who this affects: Community Managers and Installers
“Expiration Date” for Commercial Communities
What changed: For commercial communities, the member “Move Out Date” is now labeled “Expiration Date” — a better fit for tenants, employees, or contractors whose access ends on a set date rather than a move-out. Residential communities keep “Move Out Date” exactly as before.
Where to find it: CM sidebar > Members — when approving a pending member, on a member’s details screen, on the member list (the date icon’s tooltip), and when setting an end date on a pre-approved key.
What you’ll see: Everywhere the member end-date appears, the section heading, buttons, and dialog titles read “Expiration Date” instead of “Move Out Date,” and the member-list date icon switches from a moving truck to a calendar. The date field and everything else works the same way.
What you need to do: No action needed. The wording follows your community’s type automatically.
Who this affects: Community Managers of commercial communities (and Nimbio Admins viewing them)