# January 2025

> The January 2025 release of Safecube brings teams, which gather the shipments of a workspace and can limit Editors and Viewers to them, an app that shows each user what their role allows, a team filter and a Delivered status in the shipment list, a Notes page, and a full shipment payload for the NO_CONTAINERS and NO_EVENTS cases of the Container Tracking API.

## Teams of shipments

:changelog-meta{type="added" products="platform" date="2025-01-14"}

A Safecube workspace can gather its shipments into teams, to sort them by customer, business unit or product. The app calls them **Teams**; the API and the `groups` column of the CSV import call them groups.

An Admin creates, renames and deletes teams and adds their members. An Editor adds a shipment to teams from the shipment list, from its details or when creating it.

Adding a shipment to a team hides it from no one. An Editor or a Viewer with the scope **Teams** sees only the shipments of their teams, and keeps the rights of their role on them.

Teams are described in [Teams](/en/platform/workspace/teams), and the scope of a member in [Users and roles](/en/platform/workspace/users-and-roles).

## An app that follows the role of each user

:changelog-meta{type="improved" products="platform" date="2025-01-15"}

From 15 January 2025, Safecube shows each user the pages and actions their role allows, and refuses a page outside their rights, even opened from its address. A window explains the roles of the workspace.

A Viewer restricted to some shipments sees only those shipments.

The roles as they work today are described in [Users and roles](/en/platform/workspace/users-and-roles).

## Filter the shipment list by team

:changelog-meta{type="improved" products="platform" date="2025-01-20"}

The filters of the shipment list include **Filter by teams**, which keeps the shipments of one or more teams. The filter shows only when the workspace has teams, and every role can use it.

The filters are described in [Shipment list](/en/platform/shipment-views/shipment-list).

## Delivered status and automatic carrier queries

:changelog-meta{type="improved" products="platform" date="2025-01-20"}

A shipment that has arrived shows the **Delivered** status in the shipment list, and the **Delivered** tab of the list gathers every delivered shipment.

When the carrier has not answered yet at the creation of a shipment, Safecube queries it again automatically: no action is needed.

The statuses are described in [Shipping statuses](/en/platform/container-tracking/shipping-statuses), and the shipments still waiting for their carrier in [Tracking issues](/en/platform/container-tracking/tracking-issues).

## Notes page

:changelog-meta{type="added" products="platform" date="2025-01-20"}

From 20 January 2025, a Notes page gathered the notes written on the shipments of the workspace.

The notes were renamed Tasks in June 2025, and the feature was withdrawn from the app on 21 July 2025.

## Full shipment payload for NO_CONTAINERS and NO_EVENTS

:changelog-meta{type="breaking" products="container-tracking" date="2025-01-30"}

From 30 January 2025, `GET /shipment` of the Container Tracking API answers with the full shipment payload when the carrier shares no container, or no event, instead of a `200` body that held only `NO_CONTAINERS` or `NO_EVENTS` in its `message`.

The case is given in `metadata.warnings`: `NO_CONTAINERS` when no container information was received from the carrier, `NO_EVENTS` when the carrier shared containers but no events. The `containers` and `containers[].events` arrays can then be empty.

An integration that read `message` reads `metadata.warnings` instead, and accepts an empty `containers` or `containers[].events` array.

The response is described in [Retrieve shipment tracking data](/en/api/container-tracking/reference/get-shipment-detail).

## Fixes

:changelog-meta{type="fixed" products="platform"}

- The dialog that adds a shipment to teams lists the teams of the workspace.
- The support form shows an error when a request cannot be sent.
