Default View Settings are now managed directly in Views, making it easier to control what users see by default.

Previously, admins configured default views in Data Settings. Now, that functionality lives in the Views list, where you can set any view as the default without switching between different areas of the product. This update also introduces the ability for users to edit their existing views.

What’s New

• Default View Settings moved to Views (Admins):
  You’ll now find the Default View at the top of the views list.  Initially it will always default to show the Number, Submitted At, and Submitter fields in the Default View but it can always be updated to the desired Columns, Filters, and Sort logic.
  
• Configure document views before publishing

  The Document List now displays the search and view options before any documents are created.  Previously, options like Search, Sort, Columns, Filters, and Views only appeared after the first document was added. Now, you’ll see these controls as soon as you create the app, so you can configure your Default View and other views before publishing your form.
  

• Set any View as the default (Admins):
  Select a view, open the menu, and choose Update with current settings to update the default view for all users with that configuration. Or simply make the necessary changes in the Default View and choose the Update with current settings to bring in the updates.
  
• Edit saved Views (All users):
  You can now update your existing views by selecting the menu and choosing Update with current settings - this will apply any updates to the filter, column, order, etc. to that view.
  
• In-product guidance (All users):
  When visiting Data Settings, you’ll see a message pointing you to the new location.
  
  A pop-up will appear in Views to highlight these changes and help you get started.
  

We’re excited to share a new set of improvements inspired by our first-ever Interactive Design Lab at Kuali Days 2026.

This session brought together teams across Academic Ops, Build, Ready, and Research creating a new kind of collaboration. Administrators worked directly with product and engineering to share thoughtful ideas for improving the user experience—and the impact was immediate.

Our engineers jumped in during the session, working through feedback in real time and delivering meaningful enhancements based on your ideas.

Now, we’re excited to put those improvements in your hands.

What's New

View Effective Permissions for Any User

You can now view a complete breakdown of a user’s access in the new Effective Permissions tab within the Person record, making it easier to understand roles and permissions across the system. For more details, see the full announcement.

Persistent Space Sorting

Your selected sort order for apps within a Space now persists across browser sessions and is saved to your user profile—rather than being limited to a single browser session.

Wait for Calculation Inputs

Improved Bridge Testing Visibility

When testing a Bridge integration, logs now show the input and output at each step. This makes it easier to troubleshoot and validate your integrations.

Custom Titles for Workflow Branch Routes

You can now add custom route labels to individual workflow branches in the workflow builder, making it easier to understand each branch at a glance—without needing to interpret the underlying logic every time you revisit a configuration.

We’ve also added Collapse All Branches to the left step menu, so you can quickly condense your workflow for a cleaner view. When you’re ready, use Expand All Branches to open everything back up.

Sticky Table of Contents in Forms

The Form Navigation on the left side of the document now stays visible as users scroll, so they can quickly move between sections without losing their place.

This table of contents appears when you enable Turn top-level sections into pages in Form Settings.

Export People List to CSV

You can now export the People list to CSV. Filter or sort the list as needed, then download exactly what you need. Choose between 'Current View' or 'All Data' for your export.

Updated Gadget Terminology

We’ve renamed the Multiple Choice gadget to Radio Buttons to better match common terminology.

More Flexible Date Field Controls

You can now set Date field restrictions based on the Current date, giving you more dynamic control over selectable dates.  This is addition to the existing options of Specific date and Created date.

Improved Time Selection

The Time field selector now includes a dropdown with AM/PM selection, making it faster and more intuitive to enter times:

Thank You!

Your feedback made this possible. The ideas shared during the Interactive Design Lab directly shaped these improvements, and we’re excited to keep building together.

Stay tuned for more opportunities to collaborate—and more updates shaped by your input.

We’ve improved how search works in document lists to help you find the right records faster. These updates reduce noise and surface the most relevant results—especially when you know what you’re looking for.

What’s New

More precise multi-term searches
Search now uses AND logic when you enter multiple terms. Results must match all terms, not just one.

• Before: Searching “Computer Engineering” returned records with Computer or Engineering
• Now: Results include only records with Computer and Engineering

This means fewer, more relevant results.

Stronger prioritization for title matches
Results now give more weight to matches in the Title field. If a record’s title matches your search, it will appear higher in the list.  This is driven from the Form Title Field in Form Settings.

Why This Matters

• Spend less time scanning through irrelevant results
• Find exact matches faster—especially when searching by title
• Get cleaner, more focused result sets

What to Expect

• You may see fewer results for the same searches—but they’ll be more relevant
• If a search returns no results, try simplifying or adjusting your terms
• Results will be better ranked, with title matches appearing first

You’ll also see an in-product alert in the document list to highlight this update.  Also, more information can be found in the Understanding Search Functionality in Kuali article.

We’re rolling out a set of user interface updates designed to streamline your experience and give you more flexibility when working in a form or product. These updates will go live in early May 2026. If you’re an administrator, you can preview the new experience now by enabling the option in the Form tab:

We’ll also be showcasing the new UI at Kuali Days—be sure to check it out there.

What’s Changing

• Full header access from an app/product
  When you open an app or product from the main dashboard, you’ll now retain access to the full application header. This makes it easier to navigate and switch contexts without losing key controls.
  
• Collapsible left navigation in next-generation products
  Within next-generation products, you’ll have the option to collapse or hide the left navigation menu. This gives you more screen real estate when you want to focus on your work—especially helpful on smaller screens or data-heavy pages.
• Improved mobile navigation and layout
  We’ve updated the mobile layout to match recent desktop improvements. When working in a form or app on a mobile device, you can now navigate between tabs—Dashboard, Documents, Form, Workflow, and Publish—using a convenient dropdown. This makes it easier to move around the application while keeping the interface clean and easy to use on smaller screens.
  
• Cleaner Document Design
  We’ve refreshed the document experience to make it more user-friendly and easier on the eyes, helping your end users complete forms with confidence. Forms now use space more efficiently, giving you a cleaner, more condensed layout. Take a moment to review your forms and see the difference!
  

We’d Love Your Feedback

As you explore the new UI, let us know what you think. Send any questions or feedback to support@kuali.co - we’re always happy to hear from you.

You can now use the same AND / OR grouping options you already know from Document List filters when building Conditional Visibility and Branch Workflow rules.

We’ve added All of the following are true and One of the following is true to form and workflow logic. These options match what’s already available when filtering documents in a form’s Document List, bringing a familiar and consistent way to build complex conditions across the product.

Why this matters

Until now, this type of grouped logic was only available in Document List filtering. In forms and workflows, achieving similar results required nested sections or embedded branches, which made configurations harder to maintain and more error-prone.

With this update, you can:

• Use the same AND / OR pattern from Document List filters in forms and workflows
• Combine multiple conditions at the same level
• Reduce deep nesting in sections and workflow branches
• Keep complex logic easier to read and manage

How to use it

• In a form, turn on Conditional Visibility for a field or section
  
• In a workflow, add or edit a Branch step
• Add a rule and choose All of the following are true or One of the following is true
• Add multiple conditions—just like you would when building a Document List filter
  

What to do next

No changes are required to existing configurations. However, if you’ve built complex logic using workarounds, you may want to review those forms or workflows and refactor them using this new approach. This can help reduce structural complexity and improve long-term reliability.

This release brings a familiar, proven filtering model into forms and workflows—so you can build powerful logic with confidence and consistency.

We’ve improved how Short Text gadgets display longer input to make them easier to read and use.

Previously, longer text could be cut off, requiring scrolling and making the field feel incomplete. Short Text gadgets now wrap and expand to fit their content, keeping the field compact for short entries while remaining readable as text grows.

What this means for you

• Longer text is no longer cut off.
• Text wraps naturally and expands as needed.
• Short Text fields stay clean and compact when input is brief.

No action is required—this update applies automatically wherever Short Text gadgets are used.

Old Short Text Behavior

• Longer text was cut off at the edge of the gadget.
• Users had to scroll horizontally to read full content.
• The field could appear broken or hard to read

New Short Text Behavior

• Text wraps onto multiple lines.
• The gadget expands vertically as content grows.
• All text remains visible and easy to read

We wanted to make you aware of an upcoming change to how currency data is returned when accessing Document List CSV exports via the API.

We’ve already updated the frontend so that exporting the Document List as a CSV from the UI includes currency gadget values as currency (for example, dollars). Previously, currency gadgets exported as cents in the CSV (for example, $3.10exported as 310).

What’s changing for API exports

We’re now extending this same behavior to CSV exports accessed via the API.

• The CSV export endpoint is not changing.
• The output behavior is changing from exporting currency values as cents to retaining the actual currency value in the CSV.

We’re sharing this update in advance so you have time to review any scripts, integrations, or processes that consume this endpoint and make any necessary adjustments.

Preview the new behavior

You can preview the new currency format today by adding the useNewCurrencyFormat URL parameter and setting it to true.

Below are example endpoints—replace testhost with your local domain.

Current behavior (exports currency as cents):

https://testhost/app/api/v0/apps/62796f6eb75668508d66a514/62793e95b75668508d663fe8/documents.csv

New behavior (exports currency values):

https://testhost/app/api/v0/apps/62796f6eb75668508d66a514/62793e95b75668508d663fe8/documents.csv?useNewCurrencyFormat=true

Important date

As of February 2, 2026, the CSV export endpoint will default to the new currency format. At that point, the useNewCurrencyFormat parameter will no longer be required.

If you have existing API integrations that consume CSV exports, be sure to update them to handle the new currency output format before this date.

Note: Currency values will continue to be stored as cents in the database. This change only affects how values are represented in the CSV export.

You can now configure a Table Gadget as an output in an integration.  This will allow you to pull data via an integration to display in a table gadget on a form.  Tables are now an option to select when configuring an integration output and upon selecting a Table Gadget as an Output you'll need to configure json for the table into the Table Config box:

Here is an example of the format that we would expect when configuring integration data to display in a table and what you would put in the Table Config of the output:.

[  {    "formKey": "N6TZ976AN6",    "id": "a5FD9TgPi",    "label": "Example Number Gadget",    "type": "Number"  },  {    "formKey": "G89eMQD5YY",    "id": "kbo16yrfs",    "label": "Example Text",    "type": "Text"  } ]

This is a flat array of objects. Each object in the array represents a different gadget/column within the table.
Keys breakdown:

formKey: this is the key you'll end up storing the data for this gadget on. Must be unique.
id: Similarly must be unique, this one is more for internal things to work correctly.
label: Optional, this is the text that shows up at the top of the associated column.
type: This must be a valid gadget type (IE: "Text", "Url", "Number", etc).

And in this example, this is how the data should be formatted when you send to our integration services for the integration to read the data correctly.  In this example the returned data is 2 filled out rows. You'll notice that within the first data key is an array of 2 objects. Each of these objects represents a row, and in each row object there's an id key as well as a data key that has a formKey for each of the gadgets you outlined above, followed by an assigned value that is associated with that gadget on that row.

{  "data": [    {      "data": {        "N6TZ976AN6": "42",        "G89eMQD5YY": "First row example"      },      "id": "B8vj6XWz9m"    },    {      "data": {        "N6TZ976AN6": "9001",        "G89eMQD5YY": "Second row example"      },      "id": "_uintwu6RF"    }  ] }

More information can be found in the Outputs section of the Create an API Integration article.

Starting today (7/30/2025) the System Settings menu will now allow system administrators to manage their Space Administrators and Space Members, as well as allowing them to manage their existing Links. This change will only impact schools that have not purchased the Spaces functionality - schools that have already purchased the Spaces functionality will not see any change. 

How Does It Work? 

• Schools that have already purchased the Spaces functionality will not see any change. 

• For schools that have not purchased the Spaces functionality but have 1 or more product suites, 

  • System administrators will now be able to manage their Space Administrators and Space Members
  • System administrators will also be able to move items (integrations, links, and apps) between suites and spaces and manage existing links that have been added to their product suites during implementation. 

Please note, if an institution does not have Spaces turned on they will not be able to create new spaces or new links.

You now have the option to add integrations in anonymous forms that point to external data sources.  Please note, you cannot pull information from Kuali Users, Groups, or other App data in anonymous forms for security reasons.  

Once you enable the 'Create documents in this app' permission for All Anonymous Users in App Permissions you'll see that the Advanced Data Lookup gadget options in the Form designer are locked down and must be enabled:

Upon clicking 'Enable' you'll get a warning message alerting you of the risks utilizing integrations in anonymous forms.  It's important to understand that an anonymous form runs without a logged in user. That means that all backend API calls that the anonymous form makes are accessible to anyone on the internet who can determine what those urls are - sensitive data should never be shared in anonymous forms, even in the lookups.