> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/release-updates/2026/january.md).

# January

### Expanded Cost Center Management

#### Assign Cost Centers Directly to Locations

Previously, cost centers could only be assigned to individual employees or specific service instances. With this update, you can now also assign a cost center directly to a location. This means that all services linked to that location, whether they are tied to the location itself or stored in its warehouse, will inherit the assigned cost center automatically. This simplifies the management of shared resources and reduces manual work.

#### Automatic Cost Center Inheritance

Once a cost center is set for a location, it will automatically apply to all services and devices associated with that location. This includes:

• Services directly linked to the location\
• Devices stored in the location’s virtual warehouse

Services that are assigned to specific employees are not affected. They continue to use the cost center assigned to the employee. This ensures that personal assignments remain intact and are not overwritten by location-wide changes.

#### User Control During Updates

<figure><img src="/files/ejz6nSQ7sS0PjoS6meyW" alt=""><figcaption></figcaption></figure>

When you update the cost center of a location, the system asks whether existing services should also be updated. This gives you the flexibility to decide on a case-by-case basis. You can choose to apply the new cost center to all linked services or keep the current assignments. If needed, individual updates can still be made manually afterward. This feature helps avoid unintentional changes and supports more precise control.

#### Cost Center Support for Cloud Entities

You can now assign cost centers to cloud-based entities. These represent services that are not tied to a specific location or employee. They now follow the same cost center logic as other entities, making the system more consistent overall.

#### Automatic Assignment During Orders

When placing an order in the Marketplace, the system automatically pulls the relevant cost center from the selected context. This can be an employee, a location, or a cloud entity. This logic ensures that every new service receives the appropriate cost center from the start. Previously, this assignment could only happen at checkout and could not be changed in advance.

***

#### Edit Cost Centers Directly in the Marketplace Cart

Previously, when you ordered a service through the Marketplace, the system automatically assigned a cost center based on the selected employee or location. However, you had no way to change that assignment during the checkout process. If the automatically assigned cost center was incorrect or missing, you had to complete the order first and then manually update the cost center afterward on the instance level.

<figure><img src="/files/GYuXlHPoJTax24ZoZgV2" alt=""><figcaption></figcaption></figure>

This update solves that issue by allowing you to **edit the cost center directly in the cart**, before you place the order. If the system assigns a cost center automatically, you can now override it. If no cost center is assigned at all, you can define one manually on the spot.

This change gives users more flexibility and transparency during the ordering process and helps ensure that cost center data is correct from the beginning.

***

#### Filtered PDF Reports in Investment Request Approvals

You can now generate more precise PDF reports in the **Investment Request** section under **Approvals**.

Previously, when you clicked **Reports > Investment request**, the system would generate a PDF containing **all entries**, regardless of filters or selections. This was limiting for users who wanted to export only specific approvals or recommendations for sharing or documentation purposes.

With the new update, the PDF report now respects:

• Active filters\
• Manual selections in the table

Only the items that are visible in your view will be included in the exported PDF. This makes the reporting process more focused and useful, especially when handling partial approvals or communicating specific decisions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.equipme.io/release-updates/2026/january.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.