---
title: "25.12 Release Notes"
slug: "dec2025"
updated: 2026-01-08T07:37:29Z
published: 2026-01-08T07:37:29Z
canonical: "help.planful.com/dec2025"
---

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

# 25.12 Release Notes

## Planful for Marketing: Enhanced Sorting Options on the My Team Page

With this release, sorting capabilities on the **My Team** page have been expanded to give administrators clearer visibility into how user access is structured. In addition to sorting by First Name, Last Name, and Email, admins can now sort by **Permissions** and **Budgets**, making it easier to understand and review user access across multiple budgets and segments. To learn more about My Team, click [here](https://help.planful.com/planful-for-marketing/docs/administering-my-team).

This update enables:

- Sorting users by their **permission level**
- Sorting users by their **budget access**
- Support for ascending and descending sorting through the column header toggles

### How Permissions Sorting Works

Permissions follow the hierarchy: **Admin, Read-Write, Read-Only.** So**,** when sorting Admin users always group at the top (descending) or bottom (ascending).

When sorting Non-Admin users with permissions for a single budget or different budgets, (shown as multiple permission–budget combinations within the same row), they are sorted according to their highest permission level in that row i.e. Read-Write.

**Note:** A user cannot have all three permission types. Admin stands alone with full access; so users with multiple permissions will only ever have a mix of Read-Write and Read-Only, i.e., their highest permission shown is Read-Write.

**For example:**

- A user with both **Read-Write** and **Read-Only** permissions will sort as **Read-Write**
- A user with only **Read-Only** permissions will sort as **Read-Only**
- A user with **Admin** will always sort as **Admin.**

This ensures sorting accurately reflects each user’s true maximum access level.

For example, when sorting the Permissions column, a user with both *Read-Write* and *Read-Only* permissions—like “ruth”—is positioned according to their **highest permission level**, so they appear under **Read-Write** when sorted. **![](https://cdn.document360.io/0921f66c-db36-4ecd-9931-7ca61d3c3bd6/Images/Documentation/planful-for-marketing-dec-rn-image-nhh7r2w6.png)**

### How Budgets Sorting Works

Users may have access to: **All** budgets, A **specific budget,** or **Multiple budget** assignments**.** Sorting the Budgets column uses **alphabetical order** based on the value shown in the first budget dropdown in the row:

- **Ascending sort** places **“All”** at the top (alphabetically first), followed by specific budgets
- **Descending sort** reverses this order

For users with multiple budgets, sorting is based on the first budget value displayed in their row.

**Example:** When sorting the Budgets column, users with specific budgets appear first or last depending on the sort direction, while users with **All** budgets group together because **“All”** is treated as a single alphabetical value.

![](https://cdn.document360.io/0921f66c-db36-4ecd-9931-7ca61d3c3bd6/Images/Documentation/planful-for-marketing-dec-rn-image-1l6e2tg1.png)

## 

## Planful for Marketing: Enhanced Import Capabilities for Expense Groups and Campaign Forecast Updates

With this release, we’ve expanded Planful for Marketing’s import functionality to support additional Budget and Forecast updates. These improvements streamline how teams maintain Expense Groups and campaign forecasts through the import, reducing the need for manual adjustments and ensuring updates flow accurately across all budget views. To lea

### Update Expense Groups Through Import

You can now manage Expense Groups directly through the import process. Previously, Expense Groups for Budget and Forecast values could not be updated using import.

**Notes:**

- Updates are applied based on the **Expense Group ID**
- Supports importing **negative amounts** as well
- When both Budget and Forecast were initially zero, the imported Budget amount will also be applied to Forecast unless a separate Forecast value is provided.

### Update Campaign Forecasts Through Import

Forecast values for campaigns can now be updated through both manual import, alongside existing editable fields such as status, currency, GL code, allocations, mode, and custom fields.

This is compatible with both **Budget-anchor** and **Forecast-anchor** configurations. The Imported Forecast values are reflected across the Manage Page (all views), charts, Campaign Drawer, and Summary tables.

> [!NOTE]
> Notes:
> 
> - You must include the Forecast column in the import template when Forecast is the anchor during automated imports
> - Budget values are applied to Forecast automatically when both were originally zero, unless a unique Forecast amount is provided

###