📧 New campaign builder experience
Creating an e-mail campaign now starts from a new campaign modal and continues in a dedicated campaign form view, so the basics are captured in one clear place before you start designing. This is the first visible step of the new campaign builder, and it replaces the older, more scattered setup flow. Existing campaigns keep working exactly as before.
🔗 Accounting and e-invoicing connections
The Twinfield connection now runs over our standard integration broker, which gives it the same monitoring and error handling as our other accounting links. For French e-invoicing, the listing filter, the collection block and the "correct and resend" action are now all governed by the dedicated e-invoicing action permission, so the right colleagues see the right options. No reconfiguration is needed on your side.
⚙️ More say over how your CRM behaves
You can now switch off the automatic pre-filling of the contact person when an activity is created, which helps teams that deliberately leave that field empty. For customers moving over from PerfectView, the migration tool lets you enable or disable individual record types, so you can bring across only the data you actually want. Both settings are available per environment.
📱 A quicker start and a lighter app
Heavy building blocks such as charts, PDF viewing, maps and date pickers are now loaded only when you actually open them, and the app's files are served compressed again. Together that means noticeably less waiting when you open Tribe, especially on slower connections. The timeline and campaign screens also open faster than before.
🔐 Hardening around links, embeds and app connections
We completed the remediation from this year's application security review: messages coming from embedded windows are now checked against their origin, styling from untrusted HTML is isolated, and link addresses are validated before they are opened or rendered. Connected apps are also held to stricter validation of their redirect addresses, and an unused API documentation endpoint has been removed from the backend. These are defensive fixes that are already live and require no action from you.
✅ More improvements
Duplicate search on large accounts — searching for duplicates by name and address no longer times out on environments with very large numbers of records.
Clearer beta labelling — the beta notice on the timeline and on e-mail activities has been updated to reflect where the new inline e-mail experience stands.
🐛 Bugs Fixed
Adjusting an image block in a template no longer throws an error.
In the e-mail campaign layout editor, option menus now appear on top of the surrounding elements instead of behind them.
Several mail-in problems are resolved: incoming mail is no longer linked to your own organisation, messages with unusual character encodings are handled, messages without recipient details no longer block the inbox, and forwarding works as expected again.
Inviting someone to the portal no longer creates an unwanted employee card, and custom pages load correctly again.
Imports of US-formatted date columns now store the correct date instead of a wildly different one.
Bulk user invitations now report which invitations failed instead of returning an empty result, and a username is no longer cleared when no change was requested.
Lists and filters behave correctly again: a multi-select "is one of" filter actually filters, the type column filter opens without breaking the view, type dropdowns are sorted alphabetically, long lists keep loading past the first 200 rows, and reloading a list no longer duplicates rows or loses which rows were expanded.
Editing records is smoother: the cursor stays put when you type the first character in an empty required description, entering 0 in a foreign-currency amount is stored instead of clearing the converted value, discarding an edit restores the original value and clears the unsaved-changes warning, relationship chips always show their label, and attached files are no longer lost on save.
Rights and validation are applied correctly again: a "may only update own records" restriction keeps applying when sub-type rights are configured, and a mandatory relationship that was removed is now reported as missing instead of valid.
Calculations and formatting produce the right results: yearly recurrences fall in the correct month, the "time within work schedule" calculation returns a value, minimum and maximum aggregates pick the real lowest and highest value, period-between-dates no longer fails on unusual settings, address lines keep their comma when there is no postal code, and a duplicate VAT-included field has been removed.
Dashboard charts refresh their figures when the underlying dataset changes, and the widget library no longer says there are no results while the matches appear below.
Connector fixes: customer data is sent to Fortnox correctly instead of empty, and the Pennylane connection authorises without errors.
Assistant conversations no longer throw away a finished answer when it takes a little longer, and retrying a message uses the screen you are actually on.
A large batch of stability fixes removed recurring frontend and backend crashes, endless loading states, saves failing with duplicate-key errors, and memory-leak and out-of-memory situations that were causing service restarts.