Every improvement,
documented.

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.

We've added a new feature that allows you to define Device Groups for physical keys. This means that devices using an RFID tag-based authentication system, such as a key fob, card, or wristband, can be part of a device group within a community.

Grouping these devices greatly simplifies the task of assigning tags to different devices. Instead of assigning the tag to each device individually, a group is created with all these devices, and the tags are directly associated with the group, eliminating the need to assign them one by one and greatly simplifying management in communities with many users and numerous access-controlled doors.

In the employee app, a new feature has been implemented to display a list of all Community facilities' bookings for the day on the app's home screen. This way, employees who have enabled the "View bookings" feature will see a list of all the day's bookings on the main screen, eliminating the need to navigate to the "View bookings" menu option and visit each facility individually to check for reservations.

A new limit has been implemented in the reservation system. This limit allows you to define the number of different days on which a reservation can be made. This prevents a resident from making multiple reservations on more than a set number of days, even if they are able to do so according to other existing limits. The most common scenario is when you want to implement a variable time slot reservation system, allowing a resident to reserve a maximum of certain hours per day. In this case, you can limit the number of reservation days, preventing them from using those hours on different days and allowing other residents to access them as well.

We have implemented a pre-booking system for facilities managed through reservations. This system is designed to prevent abusive use of facilities by certain residents, beyond the reservation limits established in the Community regulations.
Thus, you can configure a facility to use this system for a few hours, especially during new opening time slots, and select the algorithm that will be used to allocate the pre-booking among the different requests that exist.
There are different algorithms, depending on the use of the facility in the last 30 days, 60 days, or depending on who has the oldest reservation at that facility. Among the pre-reservation requests received, Onzane will use the selected algorithm to order them and will try to award them in order, taking into account that the defined reservation limits and the possible prices that are established for the bands, whether prices per use or per service, are still being used.
When the system awards the reservation to the first applicant, both the applicant and the rest of the applicants are notified of the award.
Internally, the entire system is developed so that no failures occur in time and the necessary blocks are established during the award process, avoiding unwanted reservations.

In this new version we have fixed many small bugs that existed, thanks to the feedback from our customers, whom we thank for their interest and contributions.
We have also improved some functions, such as the implementation of pass programs, downloading budgets provided by residents, new property types and more information in the My Property section.

We have created a new feature aimed at controlling and managing passes or cards for community residents. This feature allows you to create pass programs in each community, with customized operating rules that define everything from how passes are assigned or purchased to which properties or resident profiles participate in the program. The passes can then be used by residents to grant access to certain community facilities.
In addition, these passes can have different characteristics, such as validity dates and a defined number of uses.

In addition to their uniqueness, passes can be lent between different residents, according to the program specifications. In this case, there are established acceptance, denial, revocation, and return processes that can be carried out from the app.

This feature is especially useful for communities that offer additional services to their residents, such as access to swimming pools, gyms, clubs, event rooms, or other common areas, and allows for more efficient access control, avoiding the use of traditional physical devices such as cards or cards.

We've added a new settings option to the Community. We can now enable the option to receive email notifications for Community owners by default. Until now, the default option was to have this option disabled.
This way, if this option is enabled, all new owners assigned to a property in the Community will have the option to receive email notifications enabled. They can always disable it if they wish through the app in the notifications option in their settings.
This option is designed for those communities where not all owners use the app, to ensure that everyone receives email notifications sent from the Community.

It is now possible to define in the document folders, whether a folder is common to the entire Community or if it is specific to a Property Set. Until now, all folders were common to the entire Community.
This way, it is possible to better organize documents, creating specific folders for each Property Set, and thus the residents of those properties will only see the folders that correspond to them according to the Set to which they belong.
The folders that already existed in the Community have been maintained as common to the entire Community, and from now on, new specific folders can be created for each Property Set.

We have improved the announcements function, now allowing them to be sent to different targets. Until now they could be sent to the entire Community, or to a Set of properties.

From now on they can be sent to the following targets:
- To the entire Community
- To some Sets of properties
- To some Groups of properties
- To some Properties
- To some Residents

In addition, you can now choose more complex objectives, such as sending an announcement to several sets of properties, to several groups of properties, to several individual properties and finally to several specific residents, all in a single announcement.
In this way, the sending of announcements can be much better segmented, allowing residents to receive only the announcements that interest them.

We've added a new feature that allows you to define the app's functional modules that will be activated and therefore displayed in the residents' app. Previously, these modules could only be defined globally and for tenants. Now, they can be configured individually for Owners, Tenants, and Cohabitants.

This way, each resident profile can have a different configuration of functional modules, allowing each resident to have access only to the modules that correspond to their profile. For example, an Owner may have access to community management modules that are not required for a Tenant or Cohabitant.

We have completed the use of physical keys, allowing them to be directly associated with community residents. Until now, they could be associated with employees and properties, and now they can also be associated with community residents.

This makes it possible to associate cards, key fobs, or wristbands directly with certain residents and use them if personal authentication is required. The functions that already existed for employees and properties have been adapted so that they can also be used with residents.

We have implemented a new module so that the Concierge staff can keep track of the keys, in case they are in charge of managing them.
Through this new functionality, the entries and exits of the keys that are in storage, normally in the Concierge of the Community, can be recorded. For now, employees can use the control panel to register and deregister, and record the movements of each key, so that its situation is continuously monitored.

In a future improvement, we will provide this functionality to the employee app, so that they can also control it from their mobile phones, additionally adding the possibility for the recipient of a key exit and/or entry to sign the record, keeping a record of it.

The process for making reservations from the dashboard has been improved. It now follows a similar procedure to the one used in the employee app. First, the facility is selected, then the property to be booked, and finally the resident who will be booking. This makes booking reservations much easier, as it is typically used by community staff who don't know the names of all the residents, but do know the property requesting a reservation.

We have now completed development to allow multiple seasons to be defined for a facility. A season is a period of dates within a year that define the facility's schedule for that period. Until now, there was a single season that covered the entire year, but new seasons can now be created and configured with different dates to cover the entire year. An existing season configuration can also be duplicated and another created, resulting in the same configuration but allowing for quick and easy operation.

The idea behind seasons is to allow them to be defined in cases where different seasons are needed throughout the year, so that the facility can have different schedules depending on the season. It is very common to have sports facilities with different schedules in winter and summer. This way, two seasons can now be defined for the facility (winter and summer), and each can have completely different schedules and time slots.

We've added a new option for reservations: resource reservations. Resources can be anything that can be reserved in conjunction with a facility on a mandatory basis. For example, you can now define a gastropub with six tables, and a reservation can be made for one table in the gastropub.

To reserve a resource, the facility will first need to define all the facility's possible resources and the limit on the number of resources that can be reserved per home in each time slot. Following the previous example, residents can reserve one of the available tables from the app, and when there are no more available tables, the time slot will be fully reserved.

We've added a new option in the Properties section to generate a list of these properties. This feature allows you to optionally select the property type to generate the list, or if you don't select one, all properties will be listed. After selecting the property type, you can choose the file format in which you want to generate the list, including Excel, CSV, HTML, and PDF.

Now, text can be easily selected in the app, just like in other apps. By long-pressing the required text, depending on the device's operating system, you can select and copy it for other uses. This option has been enabled in areas where text is provided by residents or administrators, such as Announcements, Incidents, and Forums.

A new feature has been added in the latest version of the app (1.4.8) to request explicit acceptance of the legal conditions for use of the application itself. This includes legal information about the identification of the owner of the website and the app, terms and conditions of use, and finally the privacy policy.

It is now mandatory for all users of the app to indicate that they have read and accept all these legal conditions to continue using the Onzane application.
In addition, a section has been added to the Settings section of the app where all these legal conditions are always updated.

Notifications for newly created incidents have been improved. It's now possible to specify who to notify depending on the neighborhood where the incident is opened. This way, if an incident is opened in a neighborhood neighborhood, only the neighbors in that neighborhood will be notified. For incidents opened by employees, the neighborhood neighborhood they have defined is taken into account, if applicable. This allows for more targeted and relevant notifications. Multiple email addresses, separated by commas, can be used to notify different email addresses.

Until now, digital keys could only be created for Access Control or Lock-type facilities. Both options allow you to create digital keys for residents, but not for facilities that have a reservation system. We've now added the ability to create digital keys for facilities that have a reservation system. These digital keys can be used in facilities such as meeting rooms, common areas, or any facility that has a reservation system. Digital keys created for these facilities can be used from the resident and employee app, as well as from the dashboard, where their use and access can be managed. It adds widely requested features such as the ability for community employees to open facilities with reservations for maintenance or any other reason.

Although the use of keys is recorded in our application, whether physical or digital, until now this usage record could not be viewed directly from the control panel. We have now added the ability to view the use of digital keys from the control panel. In the Keys, Neighbors, Properties, or Employees sections, when editing a key, you can see a new section that displays the digital key's usage. The usage section displays the date and time the key was used, as well as the name of the device on which it was used. This usage list can be filtered by date and installation if you need to search for a specific use.

Although survey results could be viewed from the dashboard during the process and at the end of the survey, these results were general and not detailed. Now, in addition to being able to view all the complete survey results, they can also be downloaded in different file formats. From the dashboard, in the Surveys section, when viewing a survey, a new Actions button appears that allows you to both view and download the complete survey results. These results include the different voting options with their different votes, including data by household and neighbor, as well as the coefficient for the households. Finally, total results are shown, including the number of votes for each option and the sum of their coefficients. These data can be downloaded in formats such as Excel, CSV, or PDF.

We have implemented an additional security system to improve the use of the application and the access control allowed from within. Until now, it was possible to access the app using the same credentials as a neighbor or employee on different devices. This means that credentials are shared between different people, and although our app provides the ability to share digital keys with third parties, users continued to share their credentials.
This provides a very weak security system, since if a user shares their credentials with another person, they can access the app and all the digital keys assigned to them.
We have now implemented a user-device linking system. This means that the first time a neighbor or employee accesses the app, a device identifier is generated that associates it with the device. This way, even if the user shares their credentials, they will not be able to access the app from another device that uses a different identifier. These identifiers are unique per device, so it will prevent a user using the same credentials from accessing the app from different devices.
This improves the security of the app and the access control to the digital keys.
If a user needs to access the app from another device, for example when they change their mobile phone, they can unlink the device by requesting permission to do so. The app itself will allow you to request permission from the administrators to change devices, keeping track of the number of times the change is requested and therefore avoiding the sharing of credentials.