> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# April 2026

> Granular team permissions, role-based scoped notifications, multilingual for every organisation, and performance built for programs at scale.

> April was about control and scale: finer permissions for your team, notifications that cut the noise, multilingual for everyone, and speed on large datasets.

As programs and teams grow, the question shifts from "can we do this" to "who is allowed to, and will it stay fast." April answered both, which is squarely our [enterprise-grade](/why/enterprise-grade) bet: easy to launch, and governed and quick enough to run a global channel.

### A new Team and users page

The redesigned Team and users page pairs a cleaner interface with much more granular permission controls and extended internal roles, so you decide exactly who on your team can see and do what. Precise access control is table stakes for [enterprise](/why/enterprise-grade) buyers, and here it is self-serve rather than a support request, so tightening access never waits on us, which keeps the program [cheap to own](/why/low-tco). See [Create an internal role](/features/access/team-management/guides/create-an-internal-role).

### Scoped notifications

Notification settings are now role-based, with an own-partners-only toggle, so each person is alerted only about the partners they own. Cutting noise is what keeps people reading Introw's notifications instead of muting them, which protects the whole engagement loop, and role-scoped control is part of running a large team [enterprise-grade](/why/enterprise-grade). Internal reach has four levels (all partners, only their own, only where they collaborate, or off), which a person can then fine-tune for themselves. See [Control who gets notified](/features/engagement/notifications/guides/control-who-gets-notified).

### Multilingual, live for every organisation

Multilingual support left beta and is now available to every organisation, with folder names, tiers, and views translating too. Every customer can now run a global program, not only the ones in an early cohort, which extends the [enterprise-grade](/why/enterprise-grade) reach of the platform to your whole base. See [Set up portal languages](/features/localization/multilingual/guides/set-up-portal-languages).

### Faster at scale

Major performance work sped up large datasets and imports of 100k or more records by moving to SQL-based aggregation and optimized list queries. Big partner programs and bulk data loads stay responsive, which is what [enterprise scale](/why/enterprise-grade) demands: thousands of partners without the product slowing down.

### Full asset version management

You can now manage every asset and folder through its whole lifecycle: archive it, restore it, permanently delete it, and roll back to any earlier version from the History timeline, where each restore is itself logged. Content in a partner program is never done changing, and version control turns a wrong or outdated file into a one-click restore rather than a scramble. Keeping this self-serve for your operators, with no ticket to us, is the [low-TCO](/why/low-tco) bet applied to content. See [Track and restore asset versions](/features/content/asset-library/guides/track-and-restore-asset-versions).

### Marketing development funds, in early access

Marketing development funds arrive in early access: budgets with pooled allocation, plus request and claim forms partners submit themselves. MDF is often the point of a program, and running it inside Introw on your CRM data keeps fund spend and the pipeline it drives in one place instead of a spreadsheet. It is one more partner motion handled without a separate tool, which keeps [total cost of ownership low](/why/low-tco). See [Set up an MDF program](/features/mdf/funds-allocation/guides/set-up-an-mdf-program), and the [request](/features/mdf/projects/guides/submit-a-proposal) and [claim](/features/mdf/claims/guides/submit-a-claim) forms.

### Also new

* Safer bulk deletes: a bulk partner delete now asks you to type "delete" to confirm, so a permanent action is always deliberate. See [Bulk-update partners](/features/partners/partner-management/guides/bulk-update-partners).