Every improvement,
documented.

We have implemented new pass models that communities can use to manage passes, membership cards, or invitations, which are often used to control access to facilities such as swimming pools and clubs.

It's now possible to create and assign residents to a property without them having access to the app or needing an email address.

We've added new options for community settings. First, there's now a Lost and Found tab that lets you define whether the community has a department, area, or person dedicated to managing lost items, such as a concierge or similar.

We have rewritten the property importer used to import a community's property list, including resident assignments. The system is now asynchronous and processes in the background, allowing for the import of very large datasets. The import process can be viewed from start to finish, showing the percentage of completion.

We've improved the feature for adding personal information for community residents. You can now add multiple phone numbers, differentiate between individuals and organizations/businesses, and add representative information.

It's now possible to add residents even if they don't have an email address. We've made email optional, but it's still required if the resident wants to access the app.

We've created a new property importer for Excel files.

It is now possible to hide Reservation facilities from the app. By default, these facilities will appear visible when created, but you can hide them by changing the "Visibility in the app" setting.

We have carried out a comprehensive review of the parcel management module, which is typically used by building staff and other building personnel to manage incoming packages and notify residents. The following improvements have been made:

• When collecting packages arriving at the building's reception desk, they can be added to the system, and the application will automatically combine them with others if there are more packages pending delivery to the same apartment or resident.
• It is now possible to optionally specify a package storage location for internal tracking.
• When delivering packages, it is possible to add a signature from the person collecting it directly on their mobile device.
• A search function has been added to the list of pending packages.
• In the package history list, a search function and filters have been added to view packages by date range and delivery status.
• It is now possible to view individual details for each package collected, including data and a photo.

We've activated the search bar at the top of the control panel. It now allows you to search among residents and providers and easily find their information.

We have launched a new module within our accounting suite dedicated to managing payments to suppliers. This section automates and improves the entire process related to contracts and their payments. This module also integrates with a new feature for defining suppliers and their contracts with the Community. The administrator can monitor received invoices, payment proposals and their execution, and due dates. All of this is integrated with the community's accounting system, automatically performing accounting entries, obtaining invoice data through artificial intelligence, and offering downloadable reports and status updates.

We've added a new tax section to our accounting module. This new feature provides assisted tax compliance for firms and communities, with real-time visibility into the status of each form. It focuses on various sections, such as Form 347, withholdings (111/190), VAT (303/390), year-end closings, and filings with real-time status updates. You can monitor and verify filings and receive alerts regarding timely submission.

We've added a dedicated reports section to our accounting module. This new feature allows you to generate operational reports for decision-making and instantly share ready-made reports with clients. It includes features such as Treasury, Delinquency, Accounting, and Tax reports with filters and Excel/PDF export.

We have modified the user profile system to allow for more granular definition of these profiles. Now, in addition to specifying which modules and sections a profile has access to, you can also specify what types of actions it can perform. Among the most common are creating, editing, and deleting. This way, you can now define profiles that restrict where and what can be done in the control panel.

It is now possible to define different bank accounts for each community, so they can be used to synchronize transactions and automate accounting reconciliation, as well as process remittances and monitor the collection of payments.

We've added a new module for community accounting management. This module is designed for the accounting control of all aspects of the community. It's typically used by property managers.
With this module, we're launching our new features dedicated to property management, where we aim to include all the functional modules that will allow property managers to fully control and manage all their communities from our platform.
Within the new accounting module, you can already create and close accounting periods, manage the chart of accounts (for which we already provide a template commonly used by homeowners' associations), add journal entries, review the general ledger, and generate various balance sheets (including exporting them).
We've also begun adding accounting automation by including an Events and Accounting Rules section that will allow you to automate accounting in the future through bank reconciliation and payments and receipts.

The Finances section of the app has been improved. Community fees and utility bills, such as water, heating, and similar services, can now be displayed directly in the app so owners can view this information and download the associated documents.
This improvement is linked to the enhancement of our third-party API, which property managers can use to synchronize financial information with Onzane. It is now possible to use the API to synchronize information about community fees and utility bills. This synchronization displays this information in a detailed list for each owner within the app, including the option to download a PDF file associated with the data.

We have carried out a complete update of the surveys module, incorporating several significant improvements to optimise its functionality and usability. The most notable new features include:

• Multi-question support: It is now possible to create surveys with multiple questions of some of the existing types.
• Support for multiple-choice questions: It is now possible to create questions that allow respondents to select multiple answers, providing greater flexibility in data collection. You can optionally define the minimum and maximum number of answers allowed.
• Support for free-text questions: You can define questions where responses are free text, allowing respondents to write whatever they consider necessary.
• Support for rating questions: It is now possible to define questions where respondents must leave a rating. You can define the rating scale between a minimum and a maximum value.
• Target audience: You can define the target audience with many more options, including multi-value selections to enable a wide range of possibilities.
• More notifications: It is now possible to notify respondents when the survey is published, when the response period starts, and also before the response period ends.
• Survey type: It is now possible to define whether the survey is public, where who has voted is recorded, or anonymous, where who has voted is not recorded and only aggregated results can be obtained.
• Response scope: It is now possible to define whether you want one response per property or one response per resident.
• Permissions: It is now possible to define more precisely which resident role can respond to surveys, beyond whether the module is enabled for that role or not.
• Show results in the app: It is now possible to define, for each survey, whether you want to show the results in the app after the response period ends.
• Attachments: It is now possible to add multiple documents as attachments to the survey, which can help improve understanding.
• Mandatory questions: It is now possible to define whether survey questions must be answered or not.
• Question clarification: It is now possible to write additional text to clarify the question for respondents.
• Improved user interface: The module interface has been redesigned to offer a more intuitive and user-friendly experience, both for administrators creating surveys and for users responding to them.
• Results: Survey results are now shown including aggregated data per question as well as a breakdown (if the survey is public).
• Generate report: It is now possible to generate an Excel report with the survey results, both the general aggregated data and the breakdown data by respondent.


These improvements make the surveys module a much more powerful and versatile tool for collecting opinions and data within the Community.

We've added support for more languages, both in the app and the control panel. German and Dutch can now be set as the languages for viewing the app or the control panel. This is already implemented in the control panel and will be available in the app in the next version.

We've modified the control panel navigation system. The communities submenu is no longer located on the side; instead, it can be accessed via a yellow button next to the name of the community being managed.
This improves the information display by providing more space and allows for the addition of more options to the menu in the future without requiring additional space.
Furthermore, the panel is easier to view on smaller devices, as the menu no longer occupies the top of the screen as it did previously.

In the documents module, we've added an improvement that allows you to choose whether or not to notify residents when a new document is created. As in other sections of the control panel, a selector is checked by default, enabling you to send this push notification to residents so they are aware of a new document in the repository.

Another improvement added to the documents module is the ability to define their visibility, meaning which resident profiles can view the documents in the app. Now, for each document, you can specify whether owners, cohabitants, or tenants have access.
This feature is compatible with the existing community settings, where you can activate different modules for each resident profile. Therefore, you can activate the Documents module for cohabitants, for example, but prevent them from viewing a specific document that is restricted to owners.

We've added a new feature to the documents module that allows you to upload and create multiple documents more quickly through a batch upload process. There's now a "New Documents in Bulk" action that lets you upload several documents at once. In addition to batch uploads, you can also select or drag and drop documents into the upload area. The system automatically adds the files and allows you to define, for each one, the document type, folder or recipient, title, and date. Furthermore, this feature also allows you to define the visibility of Community documents.

For each reservation-type facility, you can define an email address to which a notification will be sent whenever a new reservation is made. This way, administrators or facility managers can stay informed of new reservations without having to constantly access the reservation system.

We have defined a new limit for facilities requiring reservations. This limit allows you to set a maximum number of reservations a resident can make within a given period.

For example, you can set a limit of 5 reservations per resident every 15 days. This helps prevent one resident from accumulating too many reservations in a short period, thus allowing other residents to access the facilities as well.

New filters have been added to the incident listings to facilitate their search and management. For incidents within a Community, there is now a filter by Building Complex, allowing you to view only the incidents associated with a specific building complex within the Community.

Additionally, for the incident listing for all Communities (in the property managers' panel), there is now a new filter by Community, eliminating the need to navigate to a specific Community's incident section to view its incidents.

Onzane (by Shelly) lock management devices now allow you to configure the type of relay used to control opening and closing. While a "Normally Open" (NO) relay is typically used, a "Normally Closed" (NC) relay may be necessary in some cases, depending on the type of lock installed. This new option allows you to adapt the device's operation to the specific needs of each installation.

We've added a new feature that lets you view access logs directly from each facility.

You can now see, in chronological order, all event logs for a facility, across all its access points and devices. Along with the date and time of the event, the log shows the channel used, the access point and device involved, the instruction given, and detailed information about who performed the action, whether it was a key, a reservation, a pass, or an order from the control panel.