June

Update 26.06.2026 Release #2

Configurable Delivery Address Options in Self Service

Self Service requests now make a clearer distinction between the selected assignment and the actual delivery address.

The assignment is still part of the request flow and remains relevant in certain scenarios. But the place where an item is assigned is not always the same place where it should be delivered.

Previously, the selected assignment also had a strong influence on the delivery address. For example, if a user selected the company work location as the assignment, the delivery address was closely tied to that selection. Using a different delivery address was only possible in a more manual way.

With this update, the delivery address can be selected separately.

A user can keep the assignment set to the company work location, while choosing the home office as the delivery destination. The assignment remains unchanged. Only the delivery address is adjusted.

When a service user adds a product to the cart, equipme shows a delivery address dialog. Before continuing with the request, the user can select or confirm where the item should be sent.

Depending on the configuration, the following delivery address options can be available:

Company work location Home office Custom address

If custom addresses are allowed, users can enter a separate delivery address directly in the dialog.

Admins can define which of these options should be available in Self Service. The configuration is available in Portal Settings under Self Service Configuration.

This means organizations can decide which delivery destinations they want to offer to their users. For example, an admin can disable home office delivery if items should not be shipped to private addresses. Custom addresses can also be restricted if users should not be able to enter their own delivery destinations.

At least one delivery address option must remain active, so every request still has a valid delivery destination.

This gives companies more control over the Self Service order flow. Users can only choose from the delivery options that are actually supported by the organization.

At the same time, the request process becomes clearer for service users. Instead of relying on the assignment to understand where an item will be sent, the delivery address is shown as a separate step and can be confirmed before the request continues.

A typical example would be a device that should remain assigned to the company work location, while the actual delivery goes to the user’s home office. With the new delivery address selection, this can now be handled directly in the standard Self Service flow.

Multiple Reminders for Expiring Services

Email reminders for expiring services can now be scheduled more flexibly.

Until now, admins could define one reminder point for an expiring service. For example, a notification could be sent five days before the expiration date. That works for simple cases, but it can be too limited when a service requires follow up, approval, renewal or coordination with a supplier.

With this update, admins can define several reminder points for the same expiration event.

Instead of sending only one notification, reminders can now be sent at multiple stages before the service expires. A typical setup could be:

14 days before expiration 7 days before expiration 3 days before expiration 1 day before expiration

This gives responsible teams more time to react and makes expiration management less dependent on a single email.

The reminder timing is configured in the mail notification settings for expiring services. Multiple values can be entered to define when the reminder emails should be sent before the expiration date.

For example, entering 14, 7, 3, 1 will trigger reminder emails 14 days, 7 days, 3 days and 1 day before the service expires.

This is useful for services that have financial, operational or contractual impact. Teams can start reviewing the service early, then receive additional reminders as the deadline gets closer.

The result is a more reliable notification flow around expiring services. Important renewals, cancellations or follow up actions are less likely to be missed simply because one reminder arrived too early or got overlooked.

Update 19.06.2026 Release #1

Direct login with single sign on

Some users do not need to choose how they want to log in. Their company already uses a defined single sign on provider, and the right login path is clear from the start.

With direct SSO login links, you can send users straight to the right login flow.

Instead of opening equipme first and selecting the login method manually, the link already points to the selected provider.

Example:

https://app.equipme.io/sso?provider=microsoft

In this example, the login starts directly with Microsoft as the single sign on provider.

Where this helps

Direct SSO login links are useful whenever users access equipme from another place, for example from an internal help page, an intranet, a customer communication or another system that points users back to equipme.

The user gets a clearer starting point and does not have to decide which login option to choose first.

A clearer entry into equipme

This is a small change, but it removes an unnecessary step from the login process. Users can enter equipme through the login method that already matches their company setup.

For providers, this also makes it easier to place equipme links in the right context and guide users directly into the intended access path.