The Kahua 2025.3 release will be deployed to our Production environments on June 14, 2025. A preview of this functionality can be accessed at https://earlyaccesslaunch.kahua.com beginning on May 31, 2025. Please click here for more information on the Early Access program.
The release notes below are subject to change. For any changes to these notes, please see the change log at the bottom of the article.
In addition to various bug fixes, performance improvements, and minor UI updates, this release includes the updates described below in the following functional areas:
General
Added Passkey Support
Passkeys are now supported as an additional multifactor authentication (MFA) option. Passkeys allow you to prove your identity by logging in from a supported device, rather than by the use of a password. For general information on passkeys, refer to this link.
Domain administrators can continue to select any combination of MFA options for user authentication. Once enabled, users will see an option to register a passkey the next time they attempt sign on. Additionally, if passkeys are enabled on the domain, users will have the option to register new passkeys from User Settings > Security > Passkeys. Passkeys are supported for external domain authentication as well.
To enable passkeys for a domain, domain administrators navigate to the existing MFA settings in Domain Settings > Authentication > Manage Authentication Groups. They can add a new authentication group or edit an existing one. Once MFA Enabled is selected on the Authentication Group, the Passkey option appears, in addition to the previously available options of Authenticator app code and Email.
Mobile - Redesigned List and View Selection
Kahua is updating the way you can change your current list and log view within an application on mobile. Instead of tapping through multiple menus, you can now simply tap the grey space at the top of the application (where list and view name display) to open a flyout where you can select any of the lists available within your current application and any of the log views available within your current list.
Introducing the CMMC Readiness App
We are excited to introduce the CMMC Readiness App, now available upon request as part of Kahua's platform. The app is designed to help contractors prepare for and maintain CMMC Level 2 or Level 3 compliance as required by the U.S. Department of Defense (DoD).
We designed this app to help accelerate your path towards CMMC certification, providing a secure, guided workspace where you can easily upload compliance documentation, tag your evidence against CMMC control assessment objectives, track your progress, and invite others such as CMMC consultants to collaborate in a centralized tool for audit readiness. This app is designed to save your company time and money.
The CMMC Readiness App is available for both existing Kahua customers and external organizations. You can access the app in one of the following ways:
- Existing Kahua Customers - Reach out to your Kahua point of contact to request access. Once access is provided, you will be able to access the app in your existing domain through Apps > CMMC.
- External Organizations - If you are not currently a Kahua customer, you can still get access to the app for your organization. You can request a demo by emailing us at mjacobsohn@kahua.com to learn more about the app and discuss how to get started. A member of our team will follow up to better understand your needs and walk you through the app.
Administration
Added TOTP/Passkey as External Authentication Methods
We have added the ability to authenticate with TOTP and passkeys for External Domain Authentication. Domain administrators will be able to select which type of authentication method they want external domain users to use. The domain admin user will now be able to enable email, TOTP, or passkeys for external authentication methods.
Reporting
Add Tokens for CUI in Portable Views
In apps that have CUI available, we have added portable view tokens for CUI access levels.
To access the token, navigate to Configuration for the app > Portable Views > Template Tokens > Common Tokens > [Clearance]. This token can be added to a Portable View to display the CUI access level for a record.
Note: Both App Def and Template (Word) based PVs support custom text for the access levels ("Restricted", "Sensitive", "None"). However, only Template (Word) based PVs support custom text for the "Clearance Label", as the App Def PVs will eventually be deprecated.
Log View Reporting Updates
As part of a broader initiative to optimize reporting, we have made changes to log view reporting.
Users can now print a log view report only if the record count is fewer than 10,000. If the record count exceeds 10,000, the print report option will be greyed out, and users will be able to download the data in CSV format across all apps. This adjustment helps prevent potential crashes and report timeouts.
Note: This functionality was released in the 2025.2.0510 maintenance release.
Added toggle to allow all apps to be enabled for the Data Store at once
Two buttons have been added to the "Enable Applications" section of the Data Store settings. These buttons allow users to enable or disable all applications with a single click, rather than manually select the toggle for each app.
While this feature is a great time-saver, we encourage users to enable only the applications they know they will need for the Data Store. This helps prevent unnecessary resource usage and ensures that only the required tables are generated.
Document Management
Punch Lists - Punch List Workflow Enhancement: Introducing the Coordinator Role
Kahua’s Punchlist workflow has been enhanced with a new Coordinator role and routing option, offering greater flexibility for teams engaged in a collaborative process of collecting, preparing, and assigning punch list items.
By default, the new Assign to Coordinator action is hidden to preserve current behavior. It can be enabled by turning off the “Hide Assign to Coordinator” setting in the Configuration app > Settings tab.
Once enabled, this workflow is ideal for scenarios where, for example, the design team identifies and records punch list items, then forwards them to the contractor, who assigns responsibility before initiating resolution.
Punch Lists - General Improvements and Updates
We have made updates to Punch Lists that will make punch lists more intuitive and easier to use than previous iterations.
Punch List Panel Open by Default in Drawing Mode
When viewing a drawing in drawing mode within the Punchlist app, the panel displaying punch list items will now be open by default on windows, web and tablets. Users will no longer have to select the panel icon to open the panel initially.
Pinned to Current Sheet Quick Filter
We have added a new quick filter in Punch Lists Drawing Mode called Pinned to Current Sheet. This quick filter allows you to quickly filter the panel to display only punch list items on the current sheet of the drawing you are viewing.
Pins Table Updates
We have updated the Pins table in the punch list to display a link to its drawing in drawing mode, the creator of the pin, and the date the pin was added. Selecting the link from the record's detail view will take the user to the pin in drawing mode.
Unpinning Punchlist Items
We have added support for unpinning a punch list item from a drawing. In drawing mode, select a pin you'd like to unpin (or select a record from panel) and select the pencil icon to edit the punch list item record.
You will then see a new Unpin icon 
in the top right of your panel to remove the pin associated with the record without deleting the record. A prompt will appear to confirm deletion of the pin.
You can also unpin a record from within the Pins table on the record by selecting the pin and then selecting Unpin in the table header. Note that you must save the record to complete the removal of the pin.
RFIs - Coordinator Role and Workflow added to RFIs
To improve alignment with Kahua's Submittal workflow and enhance support for users managing RFIs, we've introduced a new Coordinator role along with the Assign to Coordinator action. These enhancements are available in both the Standard and ...with Owner RFI workflows.
By default, the new Assign to Coordinator action is hidden to preserve current behavior. It can be enabled by turning off the “Hide Assign to Coordinator” setting in the Configuration app > Settings tab.
Once enabled, the workflow will route RFIs from the Author to the designated Coordinator for review and final preparation before submission for response.
RFIs - New "Create Revision" Feature
In many cases, responses to an RFI prompt additional or follow-up questions, requiring users to manually create a new RFI. To streamline this process, our latest release introduces a Create Revision action for RFIs, available when an RFI is in a completed state.
This new action simplifies the creation of follow-up RFIs by:
- Automatically generating a new RFI linked to the original.
- Copying over the original RFI's Question, Answer, and Reference Files.
- Appending a revision suffix (.1, .2, etc.) to the RFI Number.
This ensures continuity and clarity, while preserving the integrity of the original record. By default, this feature is disabled and can be activated by enabling the Allow RFI Revisions option in the RFI Configuration app > Settings tab.
RFIs - Improved Consistency and Usability in RFIs
As part of our continued commitment to enhancing usability and maintaining consistency across key applications, we've introduced the following updates to both Standard and ...with Owner workflows for RFIs:
- Form Titles - Form headers have been updated to provide clearer context, helping users quickly identify the document they are viewing or editing.
- Action Buttons - Button layouts have been optimized by placing the most commonly used actions first and clearly highlighting primary actions with blue buttons and white text for improved visibility.
- Notifications - Subjects in Kahua Messages and Emails have been standardized to consistently include key details—such as document type, number, action (e.g., submitted for response, returned for clarification), and project name—ensuring recipients can easily understand the purpose of each message.
Submittals - Improved Consistency and Usability in Submittal Packages and Items
As part of our continued commitment to enhancing usability and maintaining consistency across key applications, we've introduced the following updates to both Standard and Owner-Directed workflows for Submittal Packages and Items:
- Form Titles - Form headers have been updated to provide clearer context, helping users quickly identify the document they are viewing or editing.
- Action Buttons - Button layouts have been optimized by placing the most commonly used actions first and clearly highlighting primary actions with blue buttons and white text for improved visibility.
- Notifications - Subjects in Kahua Messages and Emails have been standardized to consistently include key details—such as document type, number, revision, action (e.g., submitted for review, returned for clarification), and project name—ensuring recipients can easily understand the purpose of each message.
Submittals - Collaborative Markups Review for all Reviewers (Owner-Directed Workflow)
This is a follow-up to the Submittal Collaboration feature that was released in 24.5 for the Standard workflow configuration. A new collaboration mode has been added for markups within the Submittal Packages and Submittal Items review process for the Kahua Owner-Directed Workflow. This will allow reviewers of a submittal to add markups to Reference files concurrently without the risk of overwriting each other's work.
Details of this collaboration mode are included below:
Collaboration Mode is enabled when the Submittal Package or Submittal Item moves to the "In Review" status.
The Official Reviewer can add their own markups and Send to Consultants, and those markups will be visible to the Consultant Reviewers.
Reviewers can add markups and save concurrently while the submittal is "In Review". A reviewer's markups are not visible to other reviewers until they have Responded. Reviewers cannot edit other's markups.
Once all Consultant Reviewers have responded, the Official Reviewer can add their own markups and determine which markups are included in the Official Response. To prevent a markup from being included in the Official Response, the Official Reviewer can open the Markup Panel and select the box under "Internal" for those markups they want to be hidden.
Subcontractor Daily Work Reports -Enhanced Control Over Markups and Tax
The Subcontractor’s Daily Work Reports app allows users with Moderator permissions to apply markups and tax to Labor, Materials, and Equipment entries. Previously, markup and tax rates were applied uniformly across all items within each category.
With this release, we’re introducing line-item level control for Markups and Tax. You can now:
- Choose which individual Labor, Material, or Equipment items are taxed or marked up.
- Apply different rates to each line item as needed.
This enhancement provides greater flexibility and precision when managing project costs within daily work reports.
Cost Management
Improved the updating of Contract SOV details
This update applies to Kahua for Owner, Education, General Contractor and Subcontractors using the Kahua supplied Funding Contract and Expense Contract applications with an SOV.
When an SOV is created, the SOV details fields are copied from the contract but can get out of sync if the contract is edited. To resolve this, the following changes are being made:
- SOV Number and Description fields have been made editable. They can be manually changed at any time by editing the SOV and saving the change.
- SOV Client Contact and Contractor Contact now update from the contract when the Refresh process is run. Refreshing the SOV will still update items on the SOV. For more information on refreshing the SOV, refer to this link.
Non-SOV Pay Requests and Pay Apps - Refresh latest from Contract and COs
This update applies to Kahua for Owner, Education, General Contractor and Subcontractors using the Kahua supplied Pay Requests and Pay Apps.
Previously, when using non-SOV contracts, new contract items or edits to existing contract items did not appear on new pay requests nor could they be added to new pay requests.
To resolve this issue, we've implemented the following changes:
- New pay requests / pay apps will now copy all contract items and include previously selected change orders. Previously, new pay requests copied the previous pay request items.
- A new Refresh from Contract and COs utility will be available on the latest pay request / pay app. This utility can be used to update the latest pay request with values from the contract items and change order items. New items will be added with no progress while existing items on the pay request will persist the Work Completed This Period and related values already entered.
The update brings non-SOV based pay requests behavior in line with SOV-based pay requests.
Added Check Number and Paid Date to Pay Request and Pay App logs
This update applies to Kahua for Owner, Education, General Contractor and Subcontractors using the Kahua supplied Funding Pay Apps and Expense Pay Request applications.
The fields Check Number and Paid Date have been added to Pay Requests logs, and Check Number and Received Date have added to the Pay Apps log. These fields can be made visible on any log view. For more information on log views, refer to this link.
Bid Management
Bid Solicitation - Added setting to automatically move to Sent when Approved
A new configuration setting has been added to Applications > Bid Solicitations > Settings called "Automatic Send on Approval". This will only impact customers that have Use Solicitation Approval turned ON in configuration.
When enabled, the system will perform the following actions:
- When a user approves a Bid Solicitation (workflow action), the system will automatically send the Solicitation (workflow action).
- A log is created in the history indicating that the solicitation was Approved and Sent Automatically.
Bid Proposal - Setting to require at least one attachment on Submit
A new configuration setting has been added to Applications > Bid Proposals > Settings called "Require Reference to Submit / Re-Submit".
If enabled, the system will check the References section of a Bid Proposal when a user clicks the Submit or Re-Submit workflow actions. If there isn't at least one attachment, the user will get a validation message and be unable to submit until an attachment is uploaded.
Assets
Added the ability to mark Asset Classes as "Inactive"
Users with edit rights to the Classes - Master application in Kahua now have the ability to deactivate an asset class. This prevents future use and allows customers to manage the retirement of asset classes.
A new field has been added to the Asset Definition: Classes - Master application called "Active". This new field is defaulted to TRUE for all existing classes. Additionally, the field is hidden by default, but can be exposed within Configuration by setting the "Is Visible" flag to TRUE. The new "Active" field is also available in both the API and Import functionality for use.
When the Classes - Master record is set to inactive ("Active" = False/No), the following updates occur in Kahua:
- Classes - Master
- This application is not affected as you can still edit deactivated class records (add/remove attributes, etc.)
- Classes - Template
- If the deactivated class exists in a current template, it will be hidden from the Library anchor section. Only Classes where "Active" = True will be visible in the Library anchor section.
- Deactivated classes cannot be added to a template
- Classes - Project
- If the deactivated class exists in a current project, no functionality is affected for that project.
- You can create new Types and Assets in projects where the deactivated class existed, prior to it be marked as "Active" = FALSE.
- The deactivated class is removed from availability in the Choose Classes drop down selection that is displayed after a user clicks Add in Classes - Project.
- If the deactivated class exists in a current project, no functionality is affected for that project.
- Asset Types
- Users are able to Promote Asset Types with a deactivated class from a project to the domain.
- Any Asset Types tied to deactivated classes are still visible at the domain-level
- Users are not be able to create domain-level Asset Types for deactivated classes
- Use Domain Types
- Users are not able to pull in domain asset types from deactivated classes
- Assets
- Users are able to Promote Assets from a deactivated class from a project to the domain.
- Users are able to create new assets in projects where the deactivated class already exists.
- Users are not able to create domain level assets that are tied to asset types with deactivated classes.
- Use Domain Assets
- Users are not able to pull in domain assets if the asset is tied to an asset type with a deactivated class
Added the ability to Generate QR Codes for Assets
Users are now able to generate QR codes for Assets from Asset Manager. Select one or more assets and click Generate QR Codes from the action bar to create QR codes for each asset. The QR codes for the assets will be available in the QR Codes app.
Tag Assets via Import
Using Kahua's Import Tool, you now have the ability to tag Assets and Types to records. Specifically, in the RFIs and Submittal Items applications, new tabs have been added to the export template for the Assets and Types available in the project. You can specify which Asset or Type needs to be tagged to the record by utilizing the Kahua RowNumber feature in imports. To tag multiple Assets or Types to a single record, you can use a pipe-delimited format.
Updated Tagging Panel to Include Relevant Information
The panel that appears when you are tagging Locations, Types, and Assets in various applications has been updated to include more user-relevant information. The type of tag being assigned determines which piece of information is displayed.
'
The field that will appear for each entity is listed below:
Locations - Type (if the field is not populated, the area directly below the Location Name will be blank)
Types - Asset Class
Assets - Asset Type
Integrations
Outlook Plugin - Preserve Email Body Formatting in Kahua
When users employ the Kahua for Outlook Plug-In to add emails to Kahua and use the Copy to Message or Copy to Communications feature, the body of an email message is now preserved to match the original formatting of the email.
Additionally, if the email is added as a reference to a record in a supported Kahua app, the resulting PDF of the email also retains the original formatting of the email message.
Kahua Host Updates
All Kahua hosts have been updated with various enhancements and bug fixes. The Windows host will automatically update upon first launch after the release.
Download the appropriate app for your device:
Release Note Changes
| Date | Revision | Section | Change Description |
| May 19, 2025 | 0 | All sections | Initial publication |
| May 20, 2025 | 1 | General | Added "Introducing the CMMC Readiness App" |