Access Logs Show Why an API Open Happened
What changed: Opens made through the Nimbio API can carry a short note from whatever made them, and that note now appears on your Access Logs page.
Where to find it: CM sidebar > Access Logs — under the Description of each open.
What you’ll see: Where an API-issued open used to show only the name of the API key that made it, it can now read “delivery van at side gate” or “opened for fire inspector” beneath the description. Notes show on refused opens too — usually the row you most want explained. Opens from the apps, NFC taps and guest links are unchanged.
What you need to do: No action needed. Notes appear automatically for any integration that sends them; if you build or commission an integration, ask for notes to be included.
Who this affects: Community Managers
Limit When a Key Can Open Your Gates
What changed: You can now restrict a key to certain days and certain hours. A contractor’s key can work weekdays 6:00 AM to 6:00 PM and be refused at every other time, without you disabling and re-enabling it by hand.
Where to find it: CM sidebar > Keys > three-dot menu on a key > Access Schedule
What you’ll see: A dialog with two choices — “Always allowed”, or “Only allowed during set times”. Choose the second and you get day buttons (with Weekdays / Weekends / Every day shortcuts), a From and Until time, and an “All day on those days” option. You can add several windows to one key, so weekday mornings plus Saturday afternoons is one schedule. A plain-language summary of what you’ve built shows underneath, and the key’s gates are named at the top so you can see exactly what the schedule covers. Times follow each gate’s own local time.
Two things the dialog will tell you. If you’re scheduling your community’s main key, it warns that the schedule applies to every member in the community and asks you to tick a box confirming you understand — that one key covers everybody. And a window can’t run past midnight, so if you try to set 10:00 PM to 6:00 AM it explains that you need two windows instead: tick “Runs until midnight” on the first, and start the second at midnight.
What you need to do: No action needed — existing keys are unrestricted and stay that way until you set a schedule.
Who this affects: Community Managers, Members
A Record of Who Changed a Schedule
What changed: Every access-schedule change is recorded with who made it, what the schedule was set to, and when.
Where to find it: Nimbio staff can see it on the community’s Access Schedules tab; ask Nimbio if you need a copy.
What you’ll see: A 30-day list showing the person, the time, whether the schedule was set or cleared, and the days and hours involved.
What you need to do: No action needed.
Who this affects: Community Managers, Nimbio Admins
Your Pages Reconnect Themselves on a Phone
What changed: The community manager pages no longer get stuck showing “Connecting…” after your phone’s screen locks or you switch to another app and come back. They reconnect on their own instead of needing you to reload.
Where to find it: Anywhere in the community manager pages on a phone or tablet — this affects the whole app, not one page.
What you’ll see: You come back to your browser and your pages simply carry on working, whether you were away for a few seconds or all afternoon. Before, you’d find “Connecting…” and a spinner that never finished, and reloading was the only way out. The same recovery happens when your phone picks the signal back up after a dead spot, and when you come back to the page using the back button. Two related fixes come with it: anything that updates by itself on screen, such as gate status, now starts working again after that reconnect rather than quietly staying frozen on a page that looks fine; and the sign-in screen no longer comes back as a blank white page if its connection dropped while you were away.
What you need to do: No action needed.
Who this affects: Community Managers
API-Started Hold Opens Show on the Hold Opens Page
What changed: When a gate is held open through the Nimbio API — for example by a smart-home integration like Home Assistant — that hold now appears on the Hold Opens page as an indefinite hold open, and you can end it right there. Previously the gate would be held open but the page showed “Normal” and offered no way to stop it.
Where to find it: CM sidebar > Hold Opens
What you’ll see: A “Held Open (indefinite)” badge on the gate, a note that it will stay open until the hold is ended, and the “End Hold Open” button. The change log shows “Started an indefinite hold open via API” / “Ended the indefinite hold open via API” entries.
What you need to do: No action needed.
Who this affects: Community Managers
Scan Only Returns to Nimbio Staff
What changed: Switching a gate to Scan Only is handled by Nimbio again. The toggle that sat under each gate on your Keys page has been removed.
Where to find it: CM sidebar > Keys. The switch beneath each gate is gone.
What you’ll see: Each gate still shows its name, status and open button as before, just without the Scan Only switch. A gate that is in Scan Only mode still carries a “Scan Only” label, so you can always tell which of your gates require tapping an NFC card rather than opening from the app.
What you need to do: Nothing, unless you want a gate’s Scan Only setting changed — contact Nimbio and we’ll take care of it.
Who this affects: Community Managers
Manage Your Property From Your Phone
What changed: The community manager pages have been reworked to render properly on a phone screen, so you can run your property from the device you actually carry rather than waiting until you’re at a desk.
Where to find it: Everywhere in the community manager sidebar. The biggest differences are on Members, Access Logs, Homes, API Access, Hold Opens, Community Messenger, GuestView and GuestLinks.
What you’ll see: Any page that showed a wide table now shows each entry as a card with all of its details, instead of cutting off every column past the first two. That matters most on Access Logs, which previously couldn’t tell you which gate someone opened or whether the open succeeded — the two things the page exists to answer. Pages with tabs across the top now let you swipe through them, so the later tabs are no longer unreachable. Addresses on the Homes page read on one or two lines instead of a few characters per line, and the delete button in a home’s details — which sat past the edge of the screen and could not be tapped at all — is now within reach. The API Access page’s “Create API Key” button no longer overlaps the heading, and the Access Logs date filters no longer clip to a few letters. On the Members page, the list of names now starts at the left edge of the screen instead of sitting pushed to the right with half the width wasted. On Community Messenger, each sent message shows when it was sent on its own line with the message and sender beneath, instead of a three-column table that squeezed the message into a sliver. In GuestView settings, the descriptions under Curated Directory and GuestView Entry no longer run underneath their switches, every Short Code’s copy, open and print buttons stay on screen instead of hanging off the right edge, and the access code usage log shows each use as a card with the code, result and address all visible.
What you need to do: No action needed. Desktop is unchanged.
Who this affects: Community Managers, Nimbio Admins
GuestLinks: Shareable Access for Events and One-Off Visits
What changed: You (and your members) can now create shareable links that open your community’s gates — an Event link for a party or gathering that works only during the hours set for it, or a Limited Use link that stops working after a chosen number of uses. Visitors just tap the link; no app, no account.
Where to find it: CM sidebar > GuestLinks. It sits alongside GuestView rather than inside it, and is always available — GuestLinks works whether or not your community uses GuestView.
What you’ll see: Four tabs. Links lists every link in your community with its status (Active, Upcoming, Expired, Used up, or Turned off), plus a Create Link button that walks you through picking the backing key, the gates and the details, a copy-the-URL button, and each link’s own use history. Activity is a single feed of every attempt made on any of your links — including the ones that didn’t succeed. Settings lets you exclude specific gates from each link type, restrict limited-use links to members only, and require visitors to verify a phone number before opening. Change Log records who changed those settings and when.
What you need to do: Nothing — event links are on by default for residential communities and off elsewhere; your Nimbio admin can change that per community, and you can turn individual gates or the whole flow off any time. Any link can be shut off instantly from the list.
Who this affects: Community Managers, Members, Guests
Privacy Control, Custom Names and Access Codes Are Now Yours to Set
What changed: Three GuestView directory settings that had always read “Coming Soon” for community managers now work. Privacy Control lets your members hide themselves from the directory. Custom Names lets a member display a name of their choosing — “Unit 4B” rather than their surname. Access Codes lets you issue each member a personal code a visitor can enter to get in. Nothing about how these work changed; they were simply not yours to change until now.
Where to find it: CM sidebar > GuestView > Settings.
What you’ll see: All three switches are live instead of greyed out with a “Coming Soon” note, and they show your community’s current setting rather than always reading off. Turn Access Codes on and a new section appears below with your members’ codes, the choice of which gates a code is allowed to open, and a log of every time a code was used.
What you need to do: Nothing — all three start off, exactly as they were. Turn on whichever suits your property. One thing worth knowing before you switch Custom Names off: members who had set a display name go back to showing their real last name in the directory, so leave it on if your residents rely on it.
Who this affects: Community Managers
GuestView Change Log Only Records Real Changes
What changed: The GuestView Change Log was recording “Directory settings updated” every time somebody merely opened the GuestView settings page — two entries per visit — so a log meant to show what changed slowly filled with changes nobody made.
Where to find it: CM sidebar > GuestView > Change Log.
What you’ll see: Only genuine changes appear. Entries logged before this fix stay in the 30-day history until they age out on their own.
What you need to do: No action needed.
Who this affects: Community Managers, Admins
Access Codes Switch Fixes
What changed: Two problems with the Access Codes switch. It could get stuck reading “off” after you turned it on if the server’s confirmation was slow to arrive — clicking again simply turned it on a second time, so there was no way to turn it back off. Separately, changing it briefly reset the Privacy Control and Custom Names switches while everything reloaded.
Where to find it: CM sidebar > GuestView > Settings.
What you’ll see: The Access Codes switch reflects what you set immediately, and reverts only if the change genuinely failed. Changing one setting no longer disturbs the other two.
What you need to do: No action needed.
Who this affects: Community Managers