Organizations can now assign a new "Frontdesk External" role to external reception staff. Users with this role can view the visitor list, check visitors in and out, and send visitor invitations — but cannot access or change flows, device settings, or any other configuration. This makes it easy to give third-party front desk teams exactly the access they need, without exposing sensitive admin controls.

Booking a meeting room now comes with a redesigned attendee picker. You can search and add co-workers, select from existing visitors, or invite a brand-new guest by entering any email address — all from a single, streamlined "Attendees" field. No more switching between separate flows to include external participants in your meetings.

When a user is archived — whether manually or through directory sync (e.g. Microsoft, HR systems) — their future bookings and default desk assignments are now automatically released. This prevents "ghost bookings" from blocking desks after someone leaves the organization, saving admins from having to clean them up manually.

The Visitor Management table now shows visitor type (e.g. Interview, Contractor), check-in time, and badge-printed status directly in the table columns. Front desk staff can see key visitor information at a glance without opening individual visitor details.

Visitor Management Table: Inline Visitor Details

The Presence Dashboard now lets you toggle between "Average Attendance" and "Exact Attendance." Switch to Exact Attendance to see the precise number of days each employee was detected in the office over your selected time range — no more rounding or averages. Use the new dropdown at the top of the Presence Insights page to choose your preferred view.

Admins can now enable automatic visitor checkout at midnight. When turned on, any visitor still checked in at midnight (in your organization's timezone) is automatically checked out — so your visitor log stays clean without manual effort. Find the new toggle under Settings → Booking Settings → "Automatically check out visitors at midnight."

Parking spot bookings are no longer tied to the desk booking window. If your organisation allows parking reservations up to 100 days in advance — even if desk bookings are limited to a shorter window. An Admin can set this up under the Policy Settings page. This means employees can plan their parking further ahead without being blocked by desk booking restrictions.

Admins can now control whether Frontdesk users can also book desks and use the full webapp. A new "Allow Frontdesk users to book desks" toggle is available in Settings > Booking. When enabled, Frontdesk staff can book desks, parking, meeting rooms, and more — just like regular members. When disabled, they only see guest booking. This gives organizations full flexibility to match how their reception staff actually works.

Admins can now select multiple device authorization requests at once and approve or deny them in bulk from the dashboard. This saves significant time when onboarding many devices, especially those with automatically matched users. Unmatched devices are automatically excluded from bulk approval to prevent errors.

Admins can now manually assign users to specific teams and "pin" those assignments so they are not overwritten by the next Personio (or other directory) sync. This is ideal for exceptions — such as users who need access to a different office or should only use presence features — without having to disable the sync entirely.

Admins can now control documents and forms independently for returning visitors. Previously, documents (e.g. NDAs) and forms (e.g. visitor logs) were coupled — if one was shown again on a repeat visit, both were. Now you can configure each separately, so returning visitors only see what's actually needed. For example, skip the NDA on a second visit but still collect the visitor log.

Organizations with large device fleets can now register up to 5,000 MAC addresses — a 5× increase from the previous 1,000-device cap. This means employees with multiple devices (laptops, phones, tablets) are all counted for presence detection without hitting a limit. No action needed — the new limit is already active for all accounts.