Insights & updates from our experts
A new trust option is available for accounts that want to make their configuration items (CIs) visible to specialists, financial managers, and configuration managers of another, trusted account. A very common use case for this is when a data security account, such as Widget Data Protection of the Xurrent demo data, needs to be able to create a request when a laptop from another account within the directory structure gets stolen.

After the trust option with, in this case, Widget Data Center has been enabled, the CIs are visible in the âConfiguration Itemsâ view in Widget Data Protection and can be selected in requests, request templates, tasks, task templates, and problems. It is also possible to create a custom view in the account that is allowed to see the CIs, to filter the CIs that may be selected. In the example below, a custom view is created which contains only mobile devices.

When creating such a filter in a custom view, in this case on the Product Category column, it is immediately clear in which account the configuration items are defined.

The custom view can then easily be used in a UI extension by means of a custom-suggest field. This UI extension can then be related to a request template, for example.


A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year â but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.






.webp)





.webp)
.webp)














