Access Logs — No More Bouncing to the Community Picker
What changed: Opening Access Logs for a date range with no activity used to kick you back to the community picker. It now shows an empty list instead, so you stay on the page.
Where to find it: CM sidebar > Access Logs.
What you’ll see: When there are no events in the selected window, you get an empty table you can keep working with — adjust the start/end dates and the list refreshes — rather than being sent away from the page.
What you need to do: No action needed.
Who this affects: Community Managers
Member-Open Notifications — Know When Members Open
What changed: You can now get a notification on your own device whenever any member of your community opens, with optional quiet hours so you’re not pinged when you don’t want to be.
Where to find it: CM sidebar > Notifications. (Appears only for eligible communities.)
What you’ll see: A simple on/off switch for member-open notifications, plus a Quiet Hours list. Add one or more quiet-hours windows by choosing the days of the week and a start/end time — a range like 9:00 PM to 7:00 AM correctly wraps past midnight. Notifications you receive name the member and the gate they opened.
What you need to do: Turn on notifications and, if you’d like, add quiet hours. You’re never notified about your own opens, and quiet hours follow the local time of the gate that was opened.
Who this affects: Community Managers of communities whose property type has the feature enabled.
Community Map — Draw Where Each Gate Should Open
What changed: A new map view of your community lets you see where each gate is installed and draw the area around it. This is the groundwork for a future mobile feature that can prompt a member to open — or open automatically — as they arrive at the gate.
Where to find it: CM sidebar > Map.
What you’ll see: The page opens with a short guide that explains hands-free arrival and shows you how to set the area up well, including a diagram with one good placement and two common mistakes. Below it is a map with a marker for each gate and an adjustable circle for each one, plus an address search box above the map. Select a gate, then place its area by typing an address to jump straight there or by clicking the spot on the map — even if the gate has no saved location yet — and fine-tune by dragging the circle and resizing it to set how close someone has to be. The guidance is to place the circle just outside the gate, over the road or driveway drivers use to approach, so the gate starts opening as they arrive — not centred on the gate (opens too late) and not so large it opens while drivers are still far away. You can turn each area on or off. The “On arrival” choice (prompt to open vs. open automatically) is shown but marked “Coming soon” and isn’t selectable yet. Areas start out off until you set them up; if a gate already has a saved location, we suggest it as the circle’s starting point so you can place it in one click. The area ranges from about 100 meters across (the reliable minimum for phones) up to about 500 meters, and the size slider’s labels now sit fully inside the panel.
What you need to do: Nothing yet — the mobile arrival feature isn’t live. You can set areas up now so they’re ready when it ships.
Who this affects: Community Managers
Webhooks — Get Notified in Your Own Systems
What changed: You can now connect your community to your own software. Register one or more webhook endpoints (your URLs) and Nimbio will send them a real-time notification whenever something happens in your community — so you can trigger your own automations, dashboards, or alerts without polling.
Where to find it: CM sidebar > API Access > Webhooks tab (available when API access is enabled for your community).
What you’ll see: A Webhooks tab where you add an endpoint, choose exactly which events it should receive, and see each endpoint’s status and recent delivery history. You can subscribe to: gate sensor status changes, gate opens, failed/denied opens, new member requests, member approvals, member removals, a device going offline or coming back online, and directory/doorbell calls. Each endpoint has a “Send test” button, a delivery log, and a signing secret you can rotate. Every delivery is cryptographically signed so your server can confirm it really came from Nimbio, and an endpoint that keeps failing is automatically retried and eventually paused so it stops generating noise.
What you need to do: If you want to use webhooks, stand up an https endpoint that accepts a JSON POST, add it on the Webhooks tab, pick your events, and send a test delivery to confirm it works. Store the signing secret securely (it’s shown only once) and verify the signature on incoming requests. No action needed if you don’t use webhooks.
Who this affects: Community Managers
Cleaner Data Table Toolbars
What changed: Data tables no longer show the “Columns” and “Density” toolbar buttons; the toolbar now has just Filters and Export CSV.
Where to find it: Any table toolbar — e.g. CM sidebar > Access Logs, and the Hold Open history view.
What you’ll see: A simpler toolbar above tables with only Filters and Export CSV.
What you need to do: No action needed.
Who this affects: Community Managers, Nimbio Admins
Assign NFC Tags Straight From a Tap
What changed: When you tap a Nimbio NFC tag that hasn’t been linked to a gate yet, you can now assign it to one of your gates yourself — no need to call support. Installers can do the same for gates they set up, even if they aren’t a community manager.
Where to find it: Tap an unassigned tag with your phone, then choose “Assign this tag” — or go directly to the assignment wizard from the prompt. The wizard walks you through picking a community and gate.
What you’ll see: A short guided wizard: pick the community, pick the gate, and confirm. A success screen confirms the tag is linked, and tapping the tag again opens the gate. If you don’t manage or own any gates the tag can go to, you’ll see guidance to send the tag details to support instead.
What you need to do: Sign in if prompted, then complete the wizard. No action needed if you’d rather have support assign it — just copy the tag details from the tap screen and send them in.
Who this affects: Community Managers, Installers
Steadier Members Page
What changed: The Members page no longer switches to the Pending tab by itself or reloads the list whenever member activity happens in the background. Updates are applied quietly while you stay on the tab you’re viewing.
Where to find it: CM sidebar > Members.
What you’ll see: When a join request comes in, or a member is approved or removed, while you’re on the Members page, the list refreshes in place. You stay on the Accepted, Pending, or Removed tab you were viewing instead of being pulled to Pending.
What you need to do: No action needed.
Who this affects: Community Managers
API Access for Your Community
What changed: Community managers can now generate API keys for their community and use Nimbio’s public API to automate access — checking gate status, opening gates, listing members, sending community messages, reading key and latch statuses, and managing membership (adding a member by phone number and granting keys, granting or revoking a member’s keys, and disabling or re-enabling a member’s keys) — from their own systems.
Where to find it: CM sidebar > API Access (shown when API access is enabled for your community).
What you’ll see: A page with three tabs — Keys (create test and live keys, see when each was last used, revoke them), Call Log (every API request your community has made, filterable by mode and outcome), and Playground (run real requests safely with a test key and copy ready-made curl/JavaScript snippets for going live). The Playground covers every operation — including the member-management calls and the access-log and gate-status history calls — with member and key pickers that populate automatically from your community so you don’t have to copy IDs by hand. Each key’s secret is shown only once at creation, so you copy and store it then.
What you need to do: If you’d like API access for your community, contact Nimbio to enable it. Once enabled, create a test key and try a call in the Playground.
Who this affects: Community Managers