New Features & Improvements – April 2026

This month's work has focused on making form sharing far more flexible, expanding what external users can do, providing the IndyForms Support Team with easier ways to support customers, and tightening control over payment fields.

Below is a summary of what's new, what's improved, and what's coming next.

Form sharing has been reworked to remove one of the most common points of confusion.

Previously, if you wanted to share a form with someone who didn't have create permission, you had to tick Create Records Now first — otherwise, they'd hit a permissions error when opening the link.

Now:

The old "users will require permission to create the record" warning is gone, and external user sharing is now much smoother as a result.

As we continue to clean up our External Users permissions, this also paves the way for an even bigger simplification — we'll be removing the need to choose between Internal and Public forms when designing a form, and unifying everything into a single "Forms" experience, with access handled at the share level instead. One less decision to make up front, and one less step to think about.

Payment fields now support user and group-level edit restrictions, giving you tighter control over pricing.

You can now configure a payment field so that:

This is especially useful when admins set fixed prices on a form (such as service fees, registration costs, or licence renewals) and share the form with users who should pay — but not edit — the amount.

We've extended what you can do with external users:

This unlocks scenarios such as quarterly NDIS reviews, recurring compliance checks, or any other workflow where you need to regularly send forms to people outside your organisation without having to set it up manually each time.

When configuring submittable section notifications, IndyForms will now warn you if you've selected a group or user who won't actually be able to see the form.

This prevents notifications from being silently misconfigured and saves the "why didn't they get notified?" troubleshooting later.

Previously, when an Admin user edited a record they weren't a contributor on, the buttons at the top of the form (Save, Submit, Join as Contributor) didn't always refresh correctly — the Submit button often wouldn't appear, requiring users to save and re-open the record.

The action buttons now update in real time based on what you do inside the record.

As soon as you start editing, your contributor status updates, and the correct buttons appear, including a clear Join as Contributor option where applicable.

Behind the scenes, IndyForms has been upgraded from .NET 9 to .NET 10.

There's nothing visible to end users, but this upgrade brings:

You can now configure default print settings at the form level, so PDFs and printed records use your preferred layout straight away — without needing to adjust settings each time.

We're finalising automatic PDF email delivery, where a PDF copy of a submitted record can be emailed automatically to selected recipients (including users who don't have access to the form itself).

This will make it much easier to share completed records with colleagues, clients, or external stakeholders without having to manually download and forward them.

The document library is getting a meaningful upgrade, including:

These changes will make the document library more useful as a central operational workspace, not just a place to store files.

We're updating notification and invitation emails to send "via IndyForms" on behalf of the user who triggered them.

This means recipients will see invitations and shared forms as coming from the actual person who invited them (with replies routed back to that person's email), rather than from a generic IndyForms address. System emails (such as Daily Digests and overdue reminders) will continue to come directly from IndyForms.

A proper header design element is coming to the form builder, so you can add styled headers without dropping into raw HTML.

We're scoping SMS-based notifications and invites, including:

This is especially useful for medical, NDIS, and high-trust workflows, where recipients are more likely to act on a text than an email.

We're planning to link users to datasets, so that when you view a user, you can see all the dataset rows (and related forms) connected to them — a more CRM-style view of customer or participant data.

We're looking at a dedicated auditor-sharing model, so you can grant temporary, read-only access to specific records for audits and reviews, and then revoke it cleanly when the audit is complete.

We're planning to replace the current internal vs public form split with a single public sharing option, applied at the share level rather than the form level. This will simplify form configuration and remove a long-standing source of confusion.

The IndyForms mobile app remains on the roadmap and will be picked back up once the current sharing and notification work is bedded down.