In Taxi we group together emails by projects and mailings. A project might be "weekly newsletter" and a mailing might be "week 3". You can make multiple versions of a mailing, for example Male or Female, English or French.
For complex campaign structures, you can now organize mailings into nested folders up to 5 levels deep. Create folder hierarchies that match your workflow — organize by year, region, campaign type, or any structure that works for your team.
Organize your mailings with up to 5 levels of nested folders for flexible content organization that scales with your team's workflow.
Create folders within folders to build organizational structures like:
Each folder displays counts of child folders and mailings for at-a-glance visibility.
Navigate through nested folder structures with clear breadcrumb trails showing your current location. Click any breadcrumb element to jump directly to that level in the hierarchy.
When you delete a folder, all nested child folders and their mailings are deleted.
Team permissions also cascade — teams assigned to a parent folder automatically have access to all child folders and their mailings.
Need to remove multiple mailings or versions at once? Taxi now supports bulk delete functionality, allowing you to select and delete multiple items in a single action.
Each mailing and version card includes a checkbox for selection. Use the "Select All" checkbox to quickly select all visible items, or individually select specific items you want to remove. Once selected, click the "Delete" button to remove all selected items at once.
A confirmation dialog ensures you don't accidentally delete content, and the interface provides real-time feedback during the delete operation.
Note: Selection resets when navigating between pages or changing sort order to prevent accidental cross-page deletions.
Select multiple mailings and move them to a different project in one operation. Bulk Move saves significant time when reorganizing content, compared to moving mailings one at a time.
Available from both project pages and folder pages. The destination project must use the same Email Design System, and permissions and mailing limits are validated before the move completes.
Note: Requires the Bulk Actions feature to be enabled for your organisation. Contact your account manager or support to get started.
Tag your mailings and versions with colour-coded labels for easy categorization. Tags appear as badges on your mailing and version grids, and are fully searchable across your projects.
Create up to 100 tags per organisation. Manage tags from the mailing grid dropdown on both project and folder pages. Contact your account manager or support if you need a higher tag limit.
Tags can also be assigned to individual versions independently of mailing-level tags.
Note: Org admins can enable Mailing Tags under Organisation Settings.
Turn any parent version into a reusable Layout in your Email Design System. If you've built a version that would make a great starting point for future campaigns, you can promote it directly into a Layout.
The new Layout appears alongside your other Layouts in the EDS, ready for your team to use as a foundation for new mailings — and the source version is left unchanged.
Note: Only parent versions can be promoted — child/translation versions show a disabled menu item with a tooltip.
You can make multiple versions of an email campaign with one click. And as additional versions always inherit content from the master version, you can still update content once and have it apply to all versions.
If you've built an email version that would make a great starting point for future campaigns, you can promote it directly into a Layout within your Email Design System — without leaving your workflow.
Once created, the Layout appears alongside your other Layouts in the EDS, ready for your team to use as a foundation for new mailings. The original version is left unchanged.
Note: This feature may not be available on all plans. Contact your account manager to find out more.
Once a mailing has been signed off, locking it prevents any further changes to its content — protecting the approved version from accidental edits during the rest of its lifecycle. Lock and unlock are governed by separate team permissions (lock-mailing and unlock-mailing), so you decide who can finalise a mailing and who can reopen it.
The mailing page surfaces a Locked badge along with who applied the lock and when, and every lock and unlock event is recorded to an auditable lock history.
Some workflows need a narrow exception — a team that owns last-minute corrections after the lock has been applied. The edit-locked-mailing permission grants exactly that: members of a team holding it can continue to edit through the lock, while everyone else still sees the read-only state. No mass unlock, no force-unlock workflow disruption — the lock stays on and the audit trail is preserved.
Note: No team holds the permission by default, so existing organisations see no change until it is granted.
The Audit Log gives a consolidated, chronological record of activity across your projects and mailings — the lock history above is now one stream within it. Open it from any mailing to see events on that mailing and its versions, or from a project to see a rollup across all of its mailings.
It captures renames, moves between projects and folders, design system and template changes (before → after), access grants and revocations — including access inherited from a parent project group — exports, mailing lock and unlock, clone, and create, delete and restore. Every entry shows who performed the action, their IP address, and when.
Narrow the log by event type, by user, or by date range (it defaults to the last 30 days), and page back and forth through older and newer entries. A per-version edit row shows which team member last edited each version and when, inline alongside every other event.
Visibility is governed by a dedicated view-audit-log permission, so you decide who can see the log; organisation admins are included automatically. Entries are retained for 12 months, export activity is summarised so it stays visible after the temporary download links expire, and actions taken through the API are captured too.
Note: The Audit Log is enabled per organisation — contact your account manager or support to turn it on.
Two new per-brand levers let admins narrow the editor experience without changing the underlying org configuration — useful when one organisation runs several brands with different policies for version sets and link tracking.
Both controls live on the brand's settings page and are off by default. Existing brands see no change until an admin opts in.
Define an allowlist of org-level version sets that may be selected when creating mailings, campaigns, or templates under a given brand. The dropdowns on the mailing-creation, campaign-creation, template-creation, and translation add-on forms filter to the allowed sets only. An empty allowlist means every set is visible.
Mark individual Link Tracking Profile fields as Hide in editor and they disappear from the Document Settings sidebar, the per-link rich-text dialog, and the module sidebar — while link tracking itself stays active. The field's configured default becomes authoritative at render and export time. Saved per-link and per-version values are preserved, so toggling hide back off restores them.
Sometimes you don't need to let everyone access everything. In Taxi you can restrict access to given Projects, Mailings or Versions, as you need.
