We’ve introduced a powerful new way to standardize and control document organization across clients and projects.
Account Admins can now create and manage Document Folder Groups with system-defined, immutable folder names (e.g., Permits, SWP Narrative/Maps, Soil Reports). These groups can be assigned to divisions and made available downstream to clients and projects.
Clients can select a folder group in Client Settings and now have the option to lock that selection for all projects under the client.
When a folder group is locked at the client level:
All projects under that client must use the selected folder group
Project-level folder group selection is disabled and shown as read-only with a lock indicator
Files are never deleted, but access to obsolete folders is removed and fully audit-logged
When unlocked:
Projects may choose from any folder groups assigned to their division(s)
The client’s selected group can optionally be used as the default for new projects
Folder groups can be assigned or removed at the division level
Clients may continue to add custom client folders and reorder System, Group, and Client folders
System and Group folders are clearly labeled and protected from renaming
This update helps teams enforce consistency where needed, while still allowing flexibility when appropriate—without risking data loss or silent access changes.
We’ve enhanced the inspection form builder to support more flexible, table-based layouts.
The Question Label field is no longer required when creating or editing inspection questions. Users can now leave the label blank to support layouts where data is entered directly into response fields, such as tables or grid-style inspections.
When a question is created with a blank label:
No label text is rendered in the in-app inspection UI
No label text appears in printed or PDF inspection outputs
The question continues to function normally for:
Data entry
Validation
Data storage
Exports and reporting
This eliminates the need for placeholder text (e.g., “–” or “N/A”) and results in cleaner, more readable inspection forms.
Existing inspections and questions with labels are unaffected
Required vs. optional response behavior remains unchanged
No validation or rendering regressions for existing forms
This update gives teams greater control over inspection layout and presentation—especially for complex, table-driven inspections—while maintaining full data integrity and reporting support.
We’ve fixed an issue where compliance report exports did not fully match the data shown in the application.
When viewing the compliance report:
The report correctly displayed all matching records based on filters and pagination
However, exporting the report to PDF or Excel only included a limited subset of results
This issue was especially noticeable when:
Pagination was applied
Archived projects were included in the report
PDF and Excel exports now include the complete dataset, not just a partial page
Exported reports now accurately reflect:
Applied filters
Pagination settings
Inclusion of archived projects
On-screen report data and exported data are now fully aligned
No changes to how users configure or view compliance reports
Improved trust and consistency between in-app reporting and exported files
No impact to existing saved reports or historical data
This fix ensures compliance reports can be confidently exported and shared without missing or incomplete data.
This release includes routine security and infrastructure improvements as part of our ongoing platform maintenance.
Back to Release Notes