# February 2025

> The February 2025 release of Safecube lets users attach documents to a shipment, welcomes new users with a guided tour, lets members assign and comment notes, rebuilds the shipment details page, and adds POST /easy-shipment-asynchronous to the Webhooks API, which acknowledges an addition of shipments at once and reports the result of each one through webhook events.

## Documents on shipments

:changelog-meta{type="added" products="platform" date="2025-02-04"}

A shipment can hold documents, such as a bill of lading or an invoice. They are listed in the **Documents** block of its details page, where an Editor uploads them one file at a time.

In the shipment list, a paperclip with a number shows next to a shipment that has documents.

A document is visible to every member who sees its shipment. A member with the scope **Teams** sees only the documents of the shipments of their teams.

Documents are described in [Documents](/en/platform/workspace/documents).

## Guided tour for new users

:changelog-meta{type="added" products="platform" date="2025-02-10"}

From 10 February 2025, a window welcomed each new user of Safecube, and from 26 February 2025 a guided tour helped them get started in the app. On 24 June 2025, an onboarding menu in the sidebar took over from the tour.

Neither the tour nor the onboarding menu is part of the app today.

## Assign and comment notes

:changelog-meta{type="improved" products="platform" date="2025-02-11"}

From 11 February 2025, a note could be assigned to a user of the workspace, and the Notes page filtered the notes by assignee. From 26 February 2025, users could comment on a note.

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

## Add shipments to webhook endpoints asynchronously

:changelog-meta{type="added" products="webhooks" date="2025-02-19"}

From 19 February 2025, the Webhooks API adds shipments to one or several endpoints with `POST /easy-shipment-asynchronous`. The request is acknowledged at once with `202 Accepted` and an empty body, then processed asynchronously.

The body is an object keyed by endpoint ID (`ep_…`); each value holds a `shipments` array, and each shipment has a `number` and, optionally, a `type` and a `sealine`.

Each shipment then triggers either a `shipment.added.to.endpoint` or a `shipment.in.error` event. Subscribe the endpoint to both events to know whether each shipment was added.

The request is described in [Add shipments asynchronously](/en/api/webhooks/reference/easy-shipment/easy-shipment-add-async), and the handling of both events in [Adding shipments](/en/api/webhooks/guides/adding-shipments).

## Redesigned shipment details page

:changelog-meta{type="improved" products="platform" date="2025-02-26"}

On 26 February 2025, the shipment details page is rebuilt. A shipment that Safecube no longer updates says so on its details page.

The page as it is today is described in [Shipment details](/en/platform/container-tracking/shipment-details), and the reasons a shipment stops updating in [Update frequency](/en/platform/container-tracking/update-frequency).

## Fixes

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

- Adding a shipment to a webhook from the app works when the carrier is detected automatically.
- The details page of a bill of lading or a booking without container data displays.
