Granular, role-based permissions for Ticketing
Company admins can now control exactly what each role can do inside Ticketing, instead of a single all-or-nothing switch. You can fully hide Ticketing for a role, grant "create ticket" and "edit ticket" independently, control work order creation/editing and sending to suppliers separately, switch chat access (including internal-team chat) on or off, and decide which roles may select the entity on a work order. This lets you restrict sensitive actions to the right people - useful when building owners, suppliers, or other external users shouldn't see everything inside Ticketing.
GL account columns, filters, and faster exports on the Project Dashboard
The Project Dashboard now shows Primary and Alternate GL account as separate columns, and you can filter independently by either - with the graphs updating to match. Both columns are included in the Project Report export, and that export now runs in the background with a progress indicator, so large reports no longer time out. Especially useful for clients who track project spend across a primary and an alternate GL account.
Unit address on the supplier Ticketing dashboard
Suppliers now see a "Unit address" column on their Tickets dashboard and can search and filter by it - matching what's already shown in the client view. Locating a ticket by unit is now possible at a glance, and the related filter now works correctly.
"Reported" filter now off by default on the Ticketing Dashboard
The Ticketing Dashboard no longer opens with the "Reported" filter automatically switched on, so you see the full ticket picture right away without having to turn it off first.
Cleaner company list in the tender module
The "add new company" shortcut has been removed from the quote's company-selection screen, so companies are no longer added to your company list by accident from within an operational screen. This keeps your company data cleaner and more accurate.
New Yardi customer integration released
A new connection with Yardi automatically syncs suppliers, tenant leases, and tenant–building associations into Proprli, and exports purchase orders back to Yardi daily - removing manual data entry and keeping both systems in sync.
New Yardi environment connection
An additional Yardi environment can now sync properties, lease data, external contacts/suppliers, recoverability, and schedules into Proprli daily, and export maintenance purchase orders back to Yardi - following the same proven pattern used for other Yardi connections.
Yardi - expired-lease tenants filtered out
Tenants whose lease has already ended are no longer imported from Yardi, so the tenants tab shows only active or future leases and stays clean and current.
Adfinity - real product code selection on contracts
Contracts can now use the correct product code from the full Adfinity list instead of a single fixed value. Product codes are fetched from Adfinity and kept in sync, so contracts reflect the accurate billing/service code.
REMS - owner address restored on work orders
Work orders sent to suppliers include the property owner's address, correcting an issue where it was being sent blank.
REMS - correct correspondence address and full owner name on work orders
The entity block on work orders now shows the correspondence/postal address and the full legal owner name - on screen and in the supplier PDF - so invoicing details are accurate.
When a supplier has a known REMS contact on file, that contact is now included on the work order automatically instead of being left blank.
REMS - faster contract invoice creation
Contract invoices are now created as soon as an invoiced amount is available, rather than only once the contract fully closes - giving an up-to-date view of invoiced amounts throughout a contract with multiple invoices.
REMS - work orders on vacant units
Work orders on vacant units now send successfully, with the correct contract number attached automatically. Previously these were rejected for a missing contract number.
REMS - budget line selection fixed on contracts
The budget-line field on contracts lists its options again, so contracts submit without hitting a "budget line required" error.
Consistent supplier data across the Ticket API
The API now returns supplier data consistently regardless of which ticket endpoint is used, removing an inconsistency that could affect integrations pulling ticket data.