These release notes summarize the new features, latest updates, and bug fixes from this month in Neostella platform.
For detailed information of product-specific changes, please visit our Help Center articles.
august 19th to 24th
adoption
| Task types included in Tasks and Workflows mapping Migration mapping now includes the task type dropdown for both Time Entry and Workflow transformation maps, so task types can be aligned and migrated consistently instead of being left out of the mapping step. | |
| Legacy ID included by default in name mapping The standard mapping for an object's "name" field now includes the record's Legacy ID by default, making migrated records easier to trace back to their source system. | |
| Run panel improvements Migration specialists can now select all and filter maps directly within the execution run panel. |
communications
| Search all accessible contacts when addressing a message The "To" field's toggle can now search every contact the user has access to, instead of being limited to contacts already linked to the current project or lead. |
core
| Redesigned login, password recovery, and workspace selection The login flow has been redesigned for a simpler, clearer first-time and returning-user experience — removing redundant or conflicting controls, streamlining navigation between steps, and replacing the previous generic look with a distinctive, on-brand design. This also lays the groundwork for future in-product announcements delivered through this same experience. |
customization
| "Contains" operator available for Dropdown fields in form logic: Administrators building conditional form logic can now use the "contains" operator on Dropdown fields, matching what's already available for other field types. | |
| Project Group option hidden when not enabled for a project type: The option to create or join a Project Group no longer appears (in the UI or via the API) for project types that don't have Project Groups enabled, removing a confusing, non-functional control. | |
| Schema refresh now runs only when the schema actually changes: The full-schema refresh script that runs during migrations now triggers only when an actual schema change is detected, instead of on every migration — reducing unnecessary processing time. | |
| Views usability improvements: A heuristic evaluation of the Views experience identified around 30 usability issues across layout, interaction, and visual consistency; this release addresses that batch of improvements. |
documents
| Share an entire folder via a single link Users can generate a share link for a whole folder at once, with an optional expiration date and the ability to allow recipients to upload new documents — without requiring the recipient to have a Neostella login. Recipients get a dedicated page to browse the folder's contents (including subfolders), view and download documents, and upload new ones if permitted. | |
| Per-envelope notification settings Envelope creation now includes a Notifications control where the sender chooses which events they want to be notified about for that specific envelope, including a new notification for when an envelope is opened, with matching in-app notifications. | |
| Sender's full name shown in signature request emails Signature request emails now show the sender's first and last name alongside their email address, instead of just the bare email address. | |
| Void an envelope individually, with a filter for voided envelopes Attorneys and paralegals can now invalidate a single envelope directly from its detail panel (e.g. when a matter changes or a document needs to be redrafted), and filter the envelope list down to just the voided ones. | |
| SMS delivery option per signer Envelope senders can configure, at the individual signer level, whether that signer receives an SMS with the envelope URL. For registered contacts this requires prior SMS consent; for unregistered contacts, no consent is required but the sender sees a warning that providing a phone number authorizes SMS contact. | |
| Unified Contacts + Users list when adding envelope signers The envelope signer dropdown now combines both platform users and contacts in a single list, instead of requiring contacts to be added separately as "Unregistered Contacts." | |
| All signers expanded by default when setting signature fields Every signer's panel is now expanded by default when configuring signature fields on an envelope, instead of only the first signer's — removing extra clicks on envelopes with several signers. | |
| Send Reminder and Copy URL actions available from the envelope grid Operations staff can now send a signing reminder or copy an envelope's signing session URL directly from the grid, without opening each envelope individually. | |
| Finer control over PDF Form field values — split dates, split addresses, and substrings PDF Form templates now support the same granular field control already available in the Word Add-in: printing only part of a date field (e.g. day only, time only), mapping individual address components (street, city, state, zip) to separate form fields, and inserting a specific substring (first N, last N, or a range) of a field's value. | |
| Cherry Pick panel now supports PDF Forms The Cherry Pick review panel — letting users choose which records to include before generating a document from a multi-record object type — now works for PDF Form generation, not just Word templates. | |
| Download multiple PDFs as one merged file Selecting two or more PDF documents now offers a "Download as Merged PDF" action, with a configuration step for document order, output file name, an optional index page, and whether to save the merged result as a document record. | |
| Real-time updates for Facts lists and grids Facts lists and grids now update live via WebSocket when any user creates, updates, or deletes a fact, instead of requiring a manual page refresh — reducing stale-data conflicts when multiple people work the same matter's facts simultaneously. | |
| Optional document record when exporting Facts Exporting facts now lets users choose whether the output is saved as a document record in the platform or simply downloaded, with the post-export notification behaving accordingly; single-page fact exports also now apply the fact highlight. | |
| Conditional table rows in the Word Add-in Users can now define filtering rules (e.g. only "Active" items, amounts over a threshold, dates in a range) to control which rows from a collection are included when a Table is inserted in the Word Add-in, instead of always rendering every row. |
finance
| Fully itemized invoicing for EAJA compliance Uninvoiced items and invoice line items can now be viewed with full granularity — broken down by project, item type, task type, and user — with that same breakdown carried through to the invoice itself, supporting the itemized documentation EAJA fee petitions require. |
workflows
| Form no longer tied to a fixed task type A form can now be attached to any task inside a task template regardless of its task type — Form is an optional attribute a user adds or removes on demand, rather than its own separate task type. | |
| Task Types manageable from the Workflows view Task types can now be created and managed directly from a dedicated tab in the Workflows area, mirroring the existing tab in Finance, without needing to switch workspaces. | |
| Task type selector always reflects the current list The task type field in a task template now pulls its options live from the task types source, instead of a fixed list, so newly added or renamed types show up immediately. | |
| Consistent task type on ad hoc tasks Ad hoc tasks now carry their task type in the same structured format used by template-generated tasks, and a bug preventing the selected task type from actually being applied on creation has been fixed. | |
| Task Type now shows in the task Details sidebar: The Details sidebar no longer leaves the Type field blank when a task has a type assigned. | |
| Form field position in the Task Template Editor: A form field added to a task template now renders in the correct position, matching the intended single-column layout instead of appearing out of place. | |
| Task Type filter removed from task views: The Task Type filter has been removed from task views entirely to reduce clutter, keeping the visible filter set focused on the filters most used in day-to-day task work. |
august 18th
adoption
| Consistent schema between sample and full data Migration specialists can now trust that what they validate in a sample load is exactly what will run in the full migration, even for entities with no records. | |
| Map archived projects from legacy systems Projects imported during migration now carry over their archived status from the legacy system. | |
| System Type mapping for Person/Organization phones, emails, and addresses Migration configurators can now map the system categorization for phones, emails, and addresses so the distinction between primary, fax, and other types is preserved when contact data is imported. | |
| Per-entity record counts after migration Once a migration execution completes, users can see a breakdown of how many records were imported per entity type — contacts, documents, projects, notes, and tasks — directly from the execution detail screen. | |
| Mapping and transformation configurations moved to Arango Mapping and transformation configurations are now stored in ArangoDB instead of S3, making them faster to retrieve and easier to manage within the platform. |
communications
| Fewer Microsoft connection errors Improvements have been made to reduce errors when users connect their Microsoft accounts to the app. | |
| Auto-filled sender identifiers in email templates Users can insert placeholders for their own contact details (name, phone, email) into email templates. When an email is sent, those placeholders automatically fill in with the sender's information — no manual entry needed each time. |
customization
| Partner-managed objects in the object builder When a partner deploys objects to a client tenant as part of a partner app, they can now choose to deploy each object as standard (editable by the client admin) or as partner-managed (locked from modification). This protects partner-deployed objects from accidental changes at both the UI and API level, while keeping them visible in the object builder for reference. |
explore
| Date field filters now work in View components Fixed an issue where date-based filters in View chart components did not update or persist, which had prevented users from building components that rely on date criteria. | |
| Preview loading banner no longer persists after leaving Explore Fixed an issue where the "Generating preview results..." banner remained visible after navigating away from Explore while a report preview was still generating. | |
| Hidden fields excluded from Quick Search Quick Search now only indexes fields that are visible to users — hidden fields no longer participate in search results. | |
| Clearer report preview loading state The report preview loading experience now shows a single, consistent loading indicator; the redundant search icon has been removed from the loading state. |
finance
| Automatic tagging on generated invoice documents When an invoice document is generated, the system now automatically applies configured tags to protect and control access, ensuring invoice documents are only visible to users with appropriate permissions. | |
| Edit fixed charges and time entries from one modal Finance users can add or remove time entries and fixed charges from a draft invoice through a single edit modal. Changes are reflected immediately in the invoice summary — items amount, fixed charges amount, and total due — while the invoice stays in draft until ready to send. | |
| Add fixed charges to invoices Billing users can add fixed charges recorded on a project directly to a client invoice, alongside time entries. Fixed charges appear in a dedicated section with a breakdown of product or service, quantity, and rate, and are automatically marked as billed once included. |
workflows
| Reference related-object fields in task templates and delays Task templates and delays can now reference fields on objects related to the Context, not just the Context object itself — making templated content and scheduled timing more accurate for workflows that depend on related data. | |
| Pending tasks no longer disappear under the status filter Fixed an issue where tasks in "Pending" status did not appear in task views when the status filter was applied, causing unassigned work to go unnoticed. | |
| Task status filter defaults and Closed value fixed The task status filter now opens with a sensible default instead of the full unfiltered list, and "Closed" is now available as a selectable filter value. | |
| Task view navigation and layout refinements Redirection to a task's underlying record is now anchored to the context text instead of a separate icon, the pinned task view gains the same navigation, a "copy URL" action gives a direct link to the task, and detail field spacing is tightened for readability. | |
| Tags column and reworked task filters Task lists now show a Tags column, and Tags become a primary, always-visible filter, while the less-used Task Type filter moves into the More Filters popover. | |
| Tasks inherit tags from their template Tasks generated from a task template now automatically inherit the tags defined on that template. | |
| Filtering and search for the Workflow Templates list Users can now search templates by name, filter by the object a workflow runs over, filter by creation date, and choose whether draft templates appear alongside published ones — with the "Show Drafts" choice persisting per user across sessions. | |
| Nested automations can read the owning object Nested automations can now read the object that owns their triggering workflow, removing the need to manually re-pass or look up ownership information. | |
| Manual trigger accepts the originating record Workflows triggered from a button on a record's edit view (e.g. a Settlement record) now correctly carry the originating record with the request, so the workflow run is properly linked back to it. | |
| Tags on task templates Task template authors can label a template with one or more existing tags in the Task Template Editor; tasks created from that template pick up those tags automatically. | |
| Execution holds until nested automation succeeds A workflow execution now holds at a nested automation node until that automation reports success, and resumes automatically, instead of advancing past a transient failure or dropped event. | |
| Nested automation updates no longer break dependent workflows Workflows referencing a nested automation continue to work after that automation is updated — publishing a new version no longer silently breaks the workflows that depend on it. | |
| Tags on ad hoc tasks Users can attach tags to a task at the moment it's created ad hoc, so it's findable and filterable alongside template-generated tasks. | |
| Workflow template settings menu clarity A badge now shows at a glance whether a template is live or still in progress, with tooltips explaining the icon controls. | |
| More visibility into running executions Execution details now surface the automations and delays involved, and show which step an execution is currently on, from the executions list. | |
| Delay sidebar shows why a workflow is waiting When a workflow pauses on a timed delay, users can now see what set the end time, how it was calculated, and how much time remains — and can skip the wait to resume the workflow immediately. | |
| Optional resolution comment no longer required Fixed an issue where users were blocked from resolving a task without a comment, even when the selected outcome code was configured with an optional comment. |
august 11th
adoption
| Contact type preservation during migration Migration configurators can now map the system categorization for phones, emails, and addresses so the distinction between primary, fax, and other types is preserved when contact data is imported. Firms no longer lose how their contact communication methods were categorized in the legacy system. | |
| Welcome email flag validation during user creation Administrators can now control whether a welcome email is sent when a user is created, preventing end users from receiving premature access notifications. | |
| Threaded messages included in Notes & Tasks import Notes and tasks now import with their full message history attached, so no conversational context is lost during migration. Users can access the complete thread directly in the platform after import. |
communications
| Communications UI consistency fixes Resolved design inconsistencies across the Communications section to improve visual polish and reinforce user trust in the platform. | |
| Notification filters and management Notifications are now easier to manage with clearer unread counts, a toggle to show read or unread only, a confirmation step before marking everything as read, and a new "All" view. |
customization
| Archived context types hidden from selectors Archived context types no longer appear as selectable options when configuring an object's restrictions in the object builder. Types that are already selected are now clearly flagged as archived, and administrators can cleanly remove those restrictions. |
documents
| Filter Facts by tags Facts can now be filtered by tag in both the Facts Grid and Facts List, making it faster to surface facts relevant to a specific topic, argument, or classification. | |
| Document type and creation date added to Fact Grid The Fact Grid now displays Document Type and Document Creation Date, giving visibility into the source document without cross-referencing separately, and enabling filtering of facts by their document of origin. | |
| Delete facts from the Grid and List Facts can now be soft-deleted, individually or in bulk, from the Fact List or Fact Grid. A confirmation modal is required before deletion, and deleted facts remain auditable. | |
| Metadata prompt on duplicate document upload Uploading a duplicate document to a project now prompts for Document Type and Tags, regardless of which upload option is chosen. | |
| Messaging on Facts Facts now support the platform's standard messaging component, letting users discuss, annotate, and collaborate directly on a fact record. | |
| Sorting added to Facts List The Facts List can now be sorted by created date, created by, fact name, and fact text. | |
| Filtering added to Facts List The Facts List can now be filtered by fact text, created date, and fact date, making it easier to work through high-volume litigation matters. | |
| Tagging for Facts ]Users can now categorize and organize facts using tags directly from the Fact View. |
explore
| Open search results in a new tab Advanced Search results can now be opened in a new tab, so users can review multiple records without losing their search results. | |
| Improved Field Selector navigation experience The hierarchical field selector now collapses related objects by default, keeps sticky headers visible while scrolling, and adds visual indicators to distinguish Child Objects from Relationship Fields — making field discovery easier as the data model grows. | |
| Projects prioritized in Quick Search ranking Quick Search now ranks Projects ahead of Contacts, while preserving relevance within each object type. | |
| Special Fields respect Quick Searchable setting Emails, Phones, and Addresses now correctly honor the Quick Searchable setting under the platform's multi-value contact model. |
workflows
| Task detail shows triggering record The task sidebar now shows which record triggered the task, giving users immediate business context without tracing back through the execution. | |
| Bulk assignee changes from the All Tasks view Users can reassign a batch of tasks to another person, or clear the assignee entirely, from a single view. | |
| Consistent task filtering, sorting, and search All task views now share one predictable set of controls — filter by assignee and status, and search by task name. | |
| Filter tasks by due status Task lists can now be filtered by due status, with the ability to show or hide completed tasks on demand. | |
| Task sidebar available from the All Tasks view The task detail panel is now available from the Available Tasks (as a read-only preview) and All Tasks views, not just one place. | |
| The Personal Task Grid no longer shows "Invalid Date" in place of the actual due date. | |
| Adhoc tasks correctly auto-populate their project name again following a recent permissions update. | |
| Connections between workflow nodes can no longer be deleted from the read-only execution view. | |
| The Completion Rule node no longer triggers validation or opens for editing when viewed from a read-only workflow instance. |
august 3rd
adoption
| Undo now restores canvas edges Deleting a relationship edge on the migration canvas and then undoing that action now correctly restores the edge, instead of leaving it removed. | |
| Provisioning forms updated with new contact fields Default forms created during tenant provisioning now include the new Phones, Addresses, and Emails fields. |
automation
| Tags for automations Users can now add and remove tags on automations, making them easier to organize and find. | |
| New generic HTTP actions — PUT, PATCH, DELETE Three new generic REST API actions have been added to the automation builder, alongside the existing GET/POST actions, expanding what automations can do against external systems. | |
| Send Email action can pull from a template Users can select an email template — with project or lead information merged in — and use it directly in the Send Email automation action. | |
| Natural-language CRON Expression Builder for time-based Starting Rules When creating a time-based starting rule, users can set up a CRON schedule using natural language. (Note: this same item was already published in the Week 31 - 2026 release notes; it's listed again in this week's source page, so flagging in case it's an unintended repeat.) |
communications
| Per-channel contact preferences for Email, Fax, and SMS Sending a communication now uses the specific phone number or email address a contact has designated for that channel, instead of a single "primary" value for everything. The contact-level fax number field has also been replaced by a dedicated fax preference. | |
| SMS consent (opt-in / opt-out) SMS can now only be sent to contacts with active consent. Consent is tracked as Unknown (no record — the default for existing/imported contacts), Pending (awaiting double opt-in confirmation), Opt-in (active, SMS allowed), or Opt-out (revoked, SMS blocked). | |
| Add a new contact inline Users can create a new contact directly from the "To" field when sending an email, fax, or SMS — and create new attendees or locations directly from the Calendar. | |
| Context is preserved when emailing from a Microsoft account When an email is sent from a Microsoft account with a project or lead selected, that context is now kept instead of being overridden by association rules. | |
| Fax details UI improvements General usability improvements to how fax details are displayed. | |
| SMS project-assignment icon always visible The icon used to assign a project or lead to a message is now always visible, making it easier to spot SMS messages that still need to be assigned. |
core
| Programmatic webhook subscription management Partners can now create, list, update, and delete webhook subscriptions programmatically via API (through a new Svix proxy), removing the need to manage them manually through the UI. All endpoints are authenticated and documented. | |
| Permissions tab for Integration Users Admins can now view the permissions assigned to an Integration User directly from its detail page, using the same permissions view already available for regular users. | |
| Contact data now reflects the canonical communications model Contact tables and the user email endpoint now read phone, email, and address data from the updated canonical data structure, ensuring information continues to display and resolve correctly following the communications data migration. | |
| Merge Contacts field names back in sync Fixed a bug where field names shown on the Merge Contacts screen were out of sync with the backend, causing inconsistencies during a merge. |
customization
| Lookup Fields Administrators can add a new field type to any form that pulls a value from a related record in context — controlling where the value comes from, whether it's visible, its label, and how it drives the form's conditional logic, all without code. Users working on a record can then see that related-record value directly inside the form without switching screens. | |
| Key system field for merge fields Every record now gets an automatically assigned, system-generated Key (UUID) at creation, which administrators can reference in merge field expressions to build consistent, unique, auto-generated names — including using short segments of the key as memorable identifiers. | |
| Communication-specific field types via selector Phone, email, and address fields now support communication-specific types (e.g. Primary, Fax, Texting) through selector-based configuration, without needing new field types. | |
| Responsive card layout Cards in views now adapt automatically to available width, showing two or three per row instead of always one, so users see more information without any extra configuration. | |
| Schema conflict feedback in the object builder Conflicts such as duplicated field labels are now surfaced directly on the affected fields, on the tabs containing them, and on the save button, instead of silently blocking the save. | |
| Document relationship fields open the right screen Clicking a document referenced in a relationship field inside a form now opens the document's metadata drawer (with a dedicated icon to open the full single view in a new tab), instead of incorrectly opening the Document Custom Fields form. | |
| Project Groups configurable by project type Project Groups can now be enabled per project type in Control Center, with propagation rules centralized at the object level instead of being configured inconsistently per group. | |
| Disable submit on fully read-only forms Forms where every field is read-only now automatically disable the submit button, instead of leaving it active with nothing to submit. | |
| Leaving a Project Group no longer requires a manual refresh Old group data is now cleared automatically when a user leaves a project group. | |
| Warning when a primary project isn't selected Project Groups now show a warning if a primary project hasn't been designated. |
explore
| Report results now show field labels instead of API field names Report results previously displayed raw API field names, making them hard to interpret for users unfamiliar with internal naming conventions. Reports now show the user-friendly field label instead. | |
| Hierarchical field selection for report filters Instead of searching across every field on every related object at once, users can now drill into a specific related object first and then browse or search only within its fields — much easier to navigate as data models grow. | |
| Date-part filtering in Advanced Search & Reports Date fields can now be filtered by an individual component of the date (e.g. month, regardless of year) — useful for recurring scenarios like birthdays, anniversaries, or renewal months — while existing relative-date filtering (Created At, Updated At) is preserved. | |
| Quick Searchable configuration is now respected Disabling a field's "Quick Searchable" option now actually removes it from Quick Search, instead of leaving it searchable. | |
| Unsupported field types can no longer be marked Quick Searchable Field types that don't provide meaningful search value (e.g. booleans) can no longer be configured as Quick Searchable, reducing irrelevant results and configuration errors. | |
| Internal system objects hidden from Search & Reporting Object selectors in Explore and Reporting no longer expose internal system collections, so users only see business-relevant objects. | |
| Save an execution as a report from the visualizer Users can revisit, tweak, and re-run executions created from unsaved reports directly from the execution visualizer, then convert a refined iteration into a saved report once it's right — without needing to save multiple temporary versions along the way. |
finance
| Delete draft invoices Finance users can delete a draft invoice before it's finalized; its line items automatically return to the uninvoiced list for future invoicing. Every deletion is auto-numbered, logged in the activity history, and preserved read-only in a dedicated Deleted Drafts tab for a complete audit trail. | |
| Void sent invoices Users can void a sent invoice that needs to be invalidated (e.g. due to an error or billing change). Voiding is permanent and requires a reason; line items are released back to the uninvoiced pool, the original invoice is preserved read-only with its invoice number retained, and the action is logged to the invoice's activity history. | |
| Fixed charges on projects Case workers can add fixed charges to a project (e.g. filing fees, document requests) pulled from the product catalog with rates pre-filled; saved charges appear as Unbilled and ready for the accounting team to invoice. | |
| Download and send invoices as PDF Invoices can now be generated and downloaded as a finalized, non-editable PDF, with a preview step before download. Once downloaded, the invoice status automatically updates to "Sent" and locks from further editing to keep the shared PDF consistent with the recorded invoice. |