Certificates Dashboard Upgrade — New Filterable Table
The company-level certificates dashboard has been replaced with a modern, filterable table that gives property managers a full cross-portfolio view of all certificates in one place.
What challenge/problem does this solve for users?
The company-level certificates dashboard had only two filters, a broken search, and no reliable way to see outstanding certificates across multiple buildings — making it essentially unusable for larger portfolios.
For whom is this especially valuable?
Property managers and company admins managing certificates across large portfolios with many buildings and suppliers.
What can the feature do?
Full cross-portfolio view of all certificates in a single filterable table
Filters for supplier, status, overdue, fund/portfolio, and legally required
Persistent filter settings saved per user
Column reordering and hiding
Dynamic total count reflecting active filters
Row-level editing via a slide-in panel
Direct link to each building's own certificates dashboard
Export that reflects your active filters
What are the benefits?
Property managers can finally use the company-level certificates dashboard as a reliable cross-portfolio tool. Larger portfolios that previously couldn't use the dashboard at all now have a complete, filterable overview with one-click export.
Certificates Dashboard — Responsive Graphs
Certificate graphs on both the company-level and building-level dashboards now respond to whatever filters are currently applied, so what you see in the table matches what you see in the charts.
What challenge/problem does this solve for users?
The graphs always showed the full unfiltered dataset regardless of which filters were active, creating a confusing disconnect that made the dashboard unreliable for reporting.
For whom is this especially valuable?
Property managers and company admins who use the dashboard graphs for reporting or quick visual checks of their certificate status.
What can the feature do?
Graphs update in real time when you apply any filter
Applies to both the company-level and building-level dashboards
What you see in the table always matches what you see in the charts
What are the benefits?
Graphs and table tell the same story — no more disconnect. Property managers can confidently use the dashboard for reporting, knowing the charts reflect exactly the same filtered data as the table.
Buildings — Multiple Entities
Buildings can now have multiple legal entities assigned, with one marked as the default, so work orders and contracts can be correctly addressed to the right owner for each section of a complex property.
What challenge/problem does this solve for users?
The system only supported a single entity per building — a hard limitation for large property complexes where different floors or sections are owned by different legal entities. This forced manual workarounds and led to incorrectly addressed invoices.
For whom is this especially valuable?
Property managers and asset owners working with complex properties that have multiple legal owners — such as mixed-use buildings or large office parks.
What can the feature do?
Assign multiple legal entities to a single building
Mark one entity as the default
A dropdown appears on work orders, project contracts, and maintenance contracts whenever more than one entity exists
Default entity is pre-selected automatically
Entity list available in Building & Spaces
What are the benefits?
Property managers no longer need workarounds for multi-entity buildings. Work orders and contracts go out addressed to the correct legal entity every time, and invoicing becomes straightforward for complex properties.
System Email Language Support
A set of system emails that were still being sent in English regardless of the user's language preference have been migrated with proper translation support, so they now correctly adapt to the recipient's configured language.
What challenge/problem does this solve for users?
After the German translation rollout, customers noticed some notifications were still arriving in English because those templates were hardcoded directly in the application rather than routed through the translation system.
For whom is this especially valuable?
All clients — especially German-language users who noticed certain system emails arriving in English despite having their language preference set correctly.
What can the feature do?
System emails now adapt to the recipient's configured language
All previously hardcoded email templates have been migrated with proper translation key support
Consistent language handling across all email types
What are the benefits?
All system emails now respect the user's language preference. German-language clients — and clients in any future supported language — receive every notification in their own language, with no exceptions.
Ticketing — Shared Tenant Chat Channels
Tenant users from the same company can now read their colleagues' property-manager chat threads on shared tickets, so the full team stays informed without needing to be the original chat author.
What challenge/problem does this solve for users?
Chats were scoped per individual user — even if two colleagues from the same tenant company had access to the same ticket, each only saw their own private chat with the property manager, while colleagues' conversations were completely hidden. A misleading chat count on the dashboard made things worse.
For whom is this especially valuable?
Tenant teams where multiple colleagues manage property-related tickets and need shared visibility into conversations with the property manager. Initially available for a select customer; additional companies can be enabled on request.
What can the feature do?
Any user from the same tenant company who has access to the ticket can open and read all intra-company chat threads
Read-only access to colleagues' chat conversations with the property manager
Full two-way shared messaging will follow in a future update
What are the benefits?
Tenant teams stay aligned on conversations with property managers. No more hidden threads, no more duplicated questions, and handovers between colleagues become seamless.
Building Dashboard — Linked Fund & Portfolio Filters
The Fund and Portfolio filters on the Buildings Dashboard now interact with each other — selecting one automatically narrows the options available in the other to only what's relevant for the current view.
What challenge/problem does this solve for users?
Both filters were independent: selecting a Fund filtered the table but the Portfolio dropdown still showed all portfolios (and vice versa), making it unnecessarily hard to find the right combination.
For whom is this especially valuable?
All users working with the Buildings Dashboard, especially those managing portfolios with many funds and sub-portfolios.
What can the feature do?
Selecting a Fund limits the Portfolio dropdown to portfolios that exist within the matching buildings
Selecting a Portfolio limits the Fund dropdown to funds associated with those buildings
The interaction works in both directions
What are the benefits?
Filtering the Buildings Dashboard becomes faster and more intuitive. Users no longer have to scroll through irrelevant options or guess which Fund/Portfolio combination exists.
DataRotonde — Automatic Ticket Transitions on Updates
Updates from DataRotonde now trigger the correct ticket status transitions in Proprli, including cases where a single update should trigger two transitions at once.
What challenge/problem does this solve for users?
Status updates coming from DataRotonde had no mechanism to move a Proprli ticket through its workflow automatically. Tickets sometimes ended up in the wrong status — either no transition fired, or two fired at once — forcing manual cleanup.
For whom is this especially valuable?
Customers using the DataRotonde integration whose ticket flow depends on accurate status updates.
What can the feature do?
Maps each DataRotonde update to the correct ticket transition
Handles cases requiring two transitions from a single update
Prevents both duplicate and missed transitions
What are the benefits?
Ticket statuses match what's happening in the field. No more manually correcting mis-transitioned tickets — the ticket board becomes a trustworthy real-time view.
The Adfinity integration now sends work orders in the exact format required for Adfinity's automatic invoice reconciliation engine to match them against incoming invoices.
What challenge/problem does this solve for users?
Several fields were missing or incorrectly formatted — the GL Account source was unreliable, the PO Number lacked the required format, zero-value work orders were being pushed unnecessarily, and VAT was not included. This prevented automatic invoice matching on the Adfinity side.
For whom is this especially valuable?
Customers using the Adfinity integration for invoice reconciliation.
What can the feature do?
GL Account now pulled exclusively from the integration record
PO Numbers formatted correctly in the required [Status]/[Year]/[Number] format
Zero-value work orders are skipped automatically
Correct VAT rate included (21% by default, 6% for qualifying residential assets)
What are the benefits?
Adfinity's automatic invoice reconciliation engine can now match invoices against Proprli work orders reliably, reducing manual reconciliation effort for finance teams.
Bloxs — Sync Fix for Work Orders
Work orders are now correctly pushed to Bloxs during sync for affected customers.
What challenge/problem does this solve for users?
Work orders were silently failing to push to Bloxs despite the buildings being synced and no obvious configuration issue, causing work order data to go missing in Bloxs.
For whom is this especially valuable?
Customers using the Bloxs integration.
What can the feature do?
What are the benefits?
Work order data stays in sync between Proprli and Bloxs without manual intervention.
DataRotonde — Support for Multiple CompanyIDs
The DataRotonde client now accepts multiple CompanyIDs within a single connection, accommodating credentials that are scoped per company.
What challenge/problem does this solve for users?
The client assumed a single company context, which broke when scoped (per-company) credentials were in use — blocking correct setup for customers whose access spanned more than one CompanyID.
For whom is this especially valuable?
DataRotonde-integrated customers whose credentials cover multiple CompanyIDs.
What can the feature do?
Accepts multiple CompanyIDs as input
Routes calls correctly per CompanyID under the same connection
Works seamlessly for single-company credentials too
What are the benefits?
DataRotonde customers with scoped multi-company credentials can be set up correctly without workarounds — no need to maintain parallel connections for the same customer.
Adfinity — Graceful Handling of Missing Integration Units
The Adfinity integration no longer crashes when a unit lookup returns no result.
What challenge/problem does this solve for users?
The integration threw a fatal error whenever it tried to process a unit that wasn't found in the integration mapping, causing the entire sync run to fail.
For whom is this especially valuable?
Customers using the Adfinity integration.
What can the feature do?
What are the benefits?
Sync runs completely reliably even when individual units are missing from the mapping — no more full sync failures due to a single missing unit.
Adfinity — Ticket Description on Work Order Payload
The ticket description is now included in the work order payload sent to Adfinity.
What challenge/problem does this solve for users?
The description field was silently omitted from every push — Adfinity received the work order without any description, leaving the accounting side with no context for the order.
For whom is this especially valuable?
Customers using the Adfinity integration.
What can the feature do?
What are the benefits?
Accounting staff on the Adfinity side can see what the work order is about without having to check back in Proprli.