Release Notes | Vizito

Latest release

What's new in Vizito 2.0.6

October 27, 2026 Older versions ↓

Vizito 2.0.6 brings a rebuilt Microsoft Teams integration and lets you choose which printer to use when you print a badge via the kiosk. Visitors now decide when their photo is taken on the tablet, static QR codes are easier to share, and locations that send email from the same domain can share one DKIM setup. On top of that, this release fixes a number of issues in the backoffice and on badges, and includes a substantial round of security improvements.

New features

A rebuilt Microsoft Teams integration. We reworked the Teams integration from the ground up. Setting it up takes fewer steps, activation is more reliable and members no longer appear twice after a synchronization. You can also choose between different ways to synchronize your members, so the integration fits how your Microsoft 365 environment is organized. The setup guide in our help center has been updated to match the new procedure.
Choose your printer when printing via kiosk. When you print a badge from the backoffice with “via kiosk”, a dialog now lets you pick the device and printer to use. A device that is online is selected for you, so in most cases you just confirm. This works everywhere you can print via kiosk, including the visitor log and registered visitors.
Visitors decide when their photo is taken. On the tablet’s photo screen, the photo button now starts a countdown instead of taking the photo straight away. Visitors who need to stand back from the tablet to be framed correctly have time to get into position. The length of the countdown is a setting, so each reception can choose what works for its setup.
Copy and download your static QR codes. When you edit a static QR code under Account settings, you now see the sign-in link it points to, with a copy button, just like the pre-registration and self-registration links. A new Download button saves the QR code as an image, named after your QR code, ready to print or put on a poster.
One DKIM setup per email domain. If several of your locations send email from addresses on the same domain, they now share one DKIM setup. You publish one pair of DNS records for the domain, and every location sending from it is covered. Before, only one location per domain could be verified.
Clear instructions when an account needs activation. When a trial has ended or an account has been disabled, the tablet app, contactless sign-in and pre-registration now show a clear message explaining what happened and how an administrator can activate or renew the subscription in the backoffice, with a way to contact our support team. Once the account is active again, everything works without reinstalling or reconfiguring the app.
Cleaner account emails that reach the inbox. Account emails such as password resets, login codes and invitations no longer carry social media icons and links. They now end with our company address and a link to our help center, which helps them pass spam and phishing filters.

Bugfixes

Backoffice

The visitor log now works properly on mobile phones: the filter buttons, the “Configure fields” button and the table columns are laid out so they stay usable on a small screen.
Fixed the visitor details window showing its rows out of place when a visit has no visit type.
Fixed a misaligned field for the welcome screen buttons in the device configuration window.

Badges and printing

Printing a badge via kiosk now also works for visit types where printing at sign-in is switched off.
A numeric Cisco ISE guest Wi-Fi password, such as 4821, is now printed as it is on the badge instead of as a date.

Security, privacy and behind the scenes

After an in-depth security review of release 2.0.4, we strengthened the separation between accounts and locations across contactless sign-in, pre-registration, the API, kiosk devices and real-time updates in the backoffice, so data can only be reached from the location it belongs to.
Permission checks are stricter for users who work in more than one location and when API keys are created.
Two-factor authentication and the “SSO only” policy are now enforced on every way of signing in.
Connecting Slack and Microsoft Teams uses a more robust authorization flow, and SAML single sign-on domains are verified more strictly.
Account and billing settings that are managed by Vizito can no longer be changed from the backoffice, and complex badge layouts can no longer slow down the platform for others.
Visitor photos, signatures and uploaded images are now kept in dedicated secure storage instead of in the main database, and are only shown through authorized links. Your data retention settings remove them exactly as before.
Better protection against spam sign-ups, more reliable delivery of emails and text messages, and improved error monitoring so we can spot and fix problems faster.

Be sure to update the Vizito app on your tablet to the latest version to enjoy all the new features.

Vizito keeps getting better. On this page you’ll find the release notes for every version of our Visitor Management System (VMS): the new features we’ve added and the bugs we’ve fixed, explained in plain language.

We write these notes for the people who actually use Vizito every day, not for developers. Instead of a list of ticket numbers you’ll read what changed on the tablet at your reception desk, what changed in the backoffice, and what it means for the way you register and manage visitors. Every entry is grouped into new features first and bugfixes below, so you can see at a glance whether a release brings you something new or simply makes what you already use work better.

How updates reach you

Vizito is a cloud-based Visitor Management System, so most of a release arrives without you lifting a finger:

The backoffice updates itself. The next time you sign in at backoffice.vizito.be, you are already on the latest version. There is nothing to install and no maintenance window to plan.
The tablet app updates through the store it was installed from: the App Store on iPadOS and Google Play on Android. Leaving automatic app updates switched on is the easiest way to make sure your reception tablet keeps pace with the backoffice.
Your settings, visit types and visitor history carry over untouched. A release never asks you to reconfigure your account or re-import your registered visitors.

Because the tablet and the backoffice are updated separately, a brand new tablet feature can take a little longer to appear on a device that has not been updated yet. If something described in a release note is missing on your tablet, checking for an app update is almost always the fix.

Reading a version number

Vizito versions look like 2.0.1. The first number changes when we ship a major reworking of the product, the second when we add a meaningful set of new features, and the third for smaller feature and bugfix releases. Whatever the size of the release, the notes below cover it in full.

Requests, problems and live status

A good part of what ends up in these release notes started as a message from a customer. If a feature would make your reception run more smoothly, or if something is not behaving the way you expect, get in touch and tell us. We read everything. Curious about what is coming next? Our public roadmap shows what we are building right now and what is planned after that.

Looking for help with a feature rather than a list of what changed? The help center walks you through setting up visit types, badge printing, pre-registration, integrations and every other part of Vizito. And if you suspect something is wrong right now rather than in a past release, the Vizito system status page shows the live state of our services.