Insights & updates from our experts
This is a somewhat unusual blog post. Rather than announcing a new feature, this post explains how it is now possible to switch off some existing functionality. Since most organizations have not implemented Release Management, we have made it possible in Xurrent to hide this functionality. In fact, it is now hidden by default. To switch it on, an account administrator only needs give someone the Release Manager role of the account. As long as no one has the Release Manager role, the ‘Releases’ option of the Records console will not become visible.

In addition, change managers will not see the Release field that is part of the Change form.

As more functionality continues to be added, we felt that this was a small but helpful step to keep Xurrent’s interface clean and easy to use.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

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)











